|
That’s certainly a workable
strategy, but from a design point of view the separate “tabs” (in
reality a view stack but works on same principles) are really applications
within their own right and I would like to be able include them just by passing
their root mxml name. Also, children will be added at run time to the view
stack using the create child method so I don’t want to have to defineall
the required view helpers for applications that may not be loaded. Looks like I will have to use the view
locator 3 separate times in the execute, onResult and onFault methods… From: Dimitrios
Gianninas [mailto:[EMAIL PROTECTED] Hi, Put the
ViewHelper(s) at a higher level, I use TabNavigators and ViewStacks in several
places in my UI, but I do not have a ViewHelper per tab/stack. Just one forthe
whole bunch. Jimmy
Gianninas Software
Developer - Optimal Payments Inc. From:Michael
Herron [mailto:[EMAIL PROTECTED] Hi All Apologies for the blank post. My problem is this: When using a tab
navigator/view stack or any other component that uses deferred instantiation,
the required view helpers are not created at start up. That is, they are
children of tab navigator and not loaded until required, i.e. until the user
opens the required tab. When my commands are instantiated, they try to use the
view locator to get the required view helpers. Of course, this causes problems.
The only solutions I can see are: Are there any other workarounds/solutions? Cheers, Mike
|
- RE: [flexcoders] Cairngorm and deferred instantiation Michael Herron
- RE: [flexcoders] Cairngorm and deferred instantiation Steven Webster
- RE: [flexcoders] Cairngorm and deferred instantiat... Michael Herron
- RE: [flexcoders] Cairngorm and deferred instan... Steven Webster
- RE: [flexcoders] Cairngorm and deferred in... Michael Herron
- Re: [flexcoders] Cairngorm and deferred instantiation David Ringley

