Hi all, hi Rob.
As I work on the issue approaching it from a number of angles (also examining a
future Deep Linking), I feel necessary to detail on your replies:
According to
ADOBE FLEX 3 Adobe Flex 3 Developer Guide [page 1089]
....
You can disable history management for an entire application by setting the
value of the historyManagementEnabled property to false on the <mx:Application>
tag. When you initialize the BrowserManager to use deep linking, Flex does this
for you.
....
I ve done that as in:
<mx:Application
xmlns:mx="http://www.adobe.com/2006/mxml";
backgroundColor="0xe8e8e8" paddingTop="0"
initialize="myInit();" historyManagementEnabled="false" >
This setting of property is simply disregarded and it keeps registering
components like Accordion and TabNavigator in the HistoryManager.as
This seems a very weird thing!
Any insight please as to the reason of this behaviour?
Thanks
George
PS1: I 've followed Tracy's advice with the html wrapper to no success. Thank
you Tracy anyway.
PS2: I keep on with Alex's suggestion, as I see no way to turn off the History
Manager (at application level, or at component level)- it just keeps turned on
always.
On the other hand from
Singleton.as
/**
* @private
* Returns the singleton instance of the implementation class
* that was registered for the specified interface,
* by looking up the class in the registry
* and calling its getInstance() method.
*
* This method should not be called at static initialization time,
* because the factory class may not have called registerClass()
yet.
*/
This seems to be my exact problem
--- In [email protected], "rob_mcmichael" <rob_mcmich...@...> wrote:
>
> --- In [email protected], Alex Harui <aharui@> wrote:
> >
> > See the modules presentation on my blog. That's the shared-code problem.
> > Singletons need to be in the main app or a shared-code module.
> >
> > Alex Harui
> > Flex SDK Developer
> > Adobe Systems Inc.<http://www.adobe.com/>
> > Blog: http://blogs.adobe.com/aharui
> >
> > From: [email protected] [mailto:[email protected]] On
> > Behalf Of grg_blls
> > Sent: Wednesday, March 18, 2009 4:37 AM
> > To: [email protected]
> > Subject: [flexcoders] A ModuleLoader issue
> >
> >
> > Hi all,
> >
> > I have the following problem with my current development. A client is
> > loging in the system either as customer or admin and accordingly the main
> > application through module manager loads either "module1" or "module2".
> > If a client is logged as customer (i.e. "module1" is loaded), he is offered
> > a number of choices, leading to loading one of "module1a", "module1b", etc.
> >
> > In every case the procedure is a unload previous/load next module through:
> >
> > public function createModule(m:ModuleLoader, s:String):void{
> > m.url = s;
> > m.loadModule();
> > }
> >
> > public function removeModule(m:ModuleLoader):void {
> > m.unloadModule();
> > }
> >
> > Finally that client is logged out when finished.
> >
> > Now if he does a new login as a customer, "module1" loads and offers again
> > the customers options, but if he tries the same option (which leads to
> > loading "module1a"), an error is thrown, with the following message from
> > the Flash Player:
> >
> > An ActionScript error has occured
> > TypeError: Error #1034: Type Coercion failed: cannot convert
> > mx.managers::historymanageri...@683d219 to mx.managers.IHistoryManager.
> > at mx.managers::HistoryManager$/get
> > impl()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\HistoryManager.as:96]
> > at
> > mx.managers::HistoryManager$/register()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\HistoryManager.as:134]
> > at
> > mx.containers::ViewStack/commitProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\ViewStack.as:649]
> > at
> > mx.containers::TabNavigator/commitProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\TabNavigator.as:504]
> > at
> > mx.core::UIComponent/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:5670]
> > at
> > mx.managers::LayoutManager/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:519]
> > at
> > mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:639]
> > at Function/http://adobe.com/AS3/2006/builtin::apply()
> > at
> > mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
> > at
> > mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]
> >
> > Any ideas, as to the nature of it and where to look fixing?
> > Thanks all in advance
> >
> > George
> >
>
> Try putting this at the start of your module:
> historyManagementEnabled = false;
>
> It worked for me, but that was with a sub application (may be the same thing).
>
> Rob
>
