Hi This is way out in left field.
But it looks like you are loading the modules into the same ApplicationDomain and since the HistoryManager is a singleton based in each domain. Try including a tabnavigator in your shell application just for the hell of it. Left me know. Make sure to addChild() it then remove it after creationComplete of the application. Peace, Mike On 2/1/07, zzwi89 <[EMAIL PROTECTED]> wrote:
Hi, I have a sample online. Very scaled down, but replicates the error and where it would occur in my application. http://seanrea.net/ModuleTest/ModuleTest.html Clicking on the two buttons will switch between children of a viewstack. If you click on '2', you should get the HistoryManager error. A RAR of the project is here: http://seanrea.net/ModuleTest.rar (sorry, couldn't put the source in one file since there are several modules involved.) Although I load the modules using <mx:ModuleLoader url="/path/to/module"/>, I did try loading them manually in AS and still got the error. I have tried setting historyManagerEnabled = false on the TabNavigator to no avail. --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, Bjorn Schultheiss <[EMAIL PROTECTED]> wrote: > > forget about recompiling the framework. > > Give us some context in your application on where this error occurs > > On 02/02/2007, at 8:49 AM, zzwi89 wrote: > > > obj); > > } > > > > I cannot simply override a manager, but as this is a null object, I > > wonder if a simple fix could be to do a null check against impl and > > obj in this function. Although I can figure out how to do this, I > > can't figure out how to recompile the entire framework. > > > > I know this could be dangerous, but there doesn't seem to be any other > > fix. > > >
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
