Awesome! Immediate feedback:
Spaces on form imports is fixed.
Strangely I can't get "stay on top" to stay enabled across launches on this version now, opposite behavior of what it was, with stuck on before.
Cool. Like I said, it's not very high priority for me... but I think I have a few cases of widgets like this where the same UDO is used for one or two different widget configurations.
I've got 3 different plants working so far for some of my most common UI elements. One for the OL leds, one for stereo/mono collapse buttons, and one for buttons to trigger test audio. The only problems so far have all been chalked up to user error.
I think the biggest next step for me will be once we can import multiple xml plants. All three of these ones I have appear in almost every instrument, so they'll be good for testing multiple imports once you feel ready for it.
Are there any other specific aspects of imported plants we should be focusing on testing and putting through the wringer for you?
Also, random q: where does the help text in the xml plant definition get used/displayed, or does it?