-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ways to access theme information for the current client via macros. #3057
Comments
Here is a dump of what you would get for all the colors used by a theme and where they are used. |
That is awesome, thank you! Definitely would create a wiki page to help folks map that in their designs and recommend TinyLAF editor as an assistive tool if they need more reference. |
Wiki page for https://wiki.rptools.info/index.php/getInfo#Retrieve_theme_Information |
Will we be able to set these theme elements by macros? Tinylaf does not seem to offer access to all of these elements (probably why some of the text colors in, for example, the Dark Theme are not optimal). A more custom, in-tool theme editor would be desirable. |
Given that right now we have to restart MapTool to change themes, I think dynamically changing the theme is contingent on something like #1248 |
Nope. No plans to do so. |
I'm not really concerned with changes being dynamic (though there has been some waffling on whether this is actually not possible.) I am interested in getting at elements that tinylaf doesn't though. |
Is your feature request related to a problem? Please describe.
I want to create add-ons that fit into the MapTool User Interface beautifully (or at least seamlessly), but currently I can't dynamically adapt the colors from the current theme to my UIs.
Describe the solution you'd like
I want some way to access colors/values from the TinyLAF theme that is loaded at MapTool Startup for the client my macros run on. Preferably this would be pretty fast, so I wouldn't have to cache them ahead of time or something like that.
Perhaps this could be appended to
getInfo("client")
.Describe alternatives you've considered
Additional context
There are some requests that would impact this one:
Unless this request is trivial, If a more advanced approach to theming like in those requests above is in the pipeline this one can probably be merged or tabled until those are more mature.
The text was updated successfully, but these errors were encountered: