Could you emulate an Inspector with a WIDE field for style names.
I know… it doesn’t make sense to emulate the thousands element of an inspector JUST because the darn thing doesn’t expand horizontally and the Style name field doesn’t allow for namespaces. I was told that allowing expension was in the works 2 years ago at the CQDF by Douglas… I guess that got backlogged again…
jsonifying the whole theme stuff would allow lots of interesting capabilities too. But Objects need to be named in order to get their attributes; “style”…
Here are some of the ideas relating to these issues in the community
Some functions such as filling the prompt with the old style name when saving as new style could problably be done easily and that would save so much time. Or providing a copy icon to copy the name of the style.
Waiting for the tooltip to show the full name of the style or clicking "Rename style" with the object selected just to be able to read the style full name is such a bore!
Shorter names are not a solution as they are not precise enough.
I use the namespace edit or input or required or display or boxedForm to identify styles of a same purpose but they take a lot of room but since I want to keep it human readable for other developer I can't really shorten to E. D. I. R. bF. , we need words like active inactive to identify the purpose, and because the same style must be applied to several object that may be used in each other stead, buttons, edit boxes, dropdown popup menu and text box the suffix .btn .bar ebx ddn pup must be added at the end because a Theme cannot have two identical styles.
