dhl83 I suppose the method you are describing (two instances of Starling and two instances of my theme), has to be implemented using pure AS3 and not using the mxml "version" of Feathers?
The creation of the second Starling instance will need to be done in AS3, but I don't see why the "root" component for that Starling instance couldn't be an MXML component. You could create a component with <f:LayoutGroup>
or something, and then pass the class to Starling's constructor (or to its rootClass
property after context creation, possibly).
Take a look at the StarlingBootstrap
class in the Feathers SDK to see how I set up the application class in the main window. The process for another window will probably be very similar.
https://github.com/feathersui/feathersui-starling-sdk/blob/master/frameworks/projects/feathers-mxml/source/feathers/core/StarlingBootstrap.as
I can see that I wait for the context to be created, then instantiate the theme, then set rootClass
. Your code will probably look a lot like that.
dhl83 You don't by any chance have your old prototype code (of a multi window Feathers desktop app) published somewhere on the web? Thank you again for your work and your quick response to my post!
No, I never published that code, and it was probably just in my personal "sandbox" project on my local machine that I use for testing random ideas, so it would have been deleted the next time that I had a new idea to play around with.