Thanks for the help you got me thinking. I can't shut off the
browsermanager entirely as I will probably need it in the future. The
issue is with the history.js file and our app. Our app runs an ajax
type animation that changes the fragment every 30 seconds. Well with
IE7 when browsermanager calls setup(initialValue:string, something
else) it sets the default fragment. Mine in this case is blank so it
put www.url.com/myflex# . Well then our ajax would ad to it and if I
clicked something to navigate as well then I ended up with
www.url.com/myflex##new_area_navigated to.

If you wait for our app to stop the ajax to stop then click something
all is fine and it replaces the entire fragement.

IE would freak out and IFrame would start trying to figure out what is
going on and report back to flex and was in a never ending loop. If I
then clicked something else in my flex app the fragment would clear
out and put just a new #somethingelse and all would be fine.

So I went into the history.js file and commented out the code to set
the #initialvalue to the url so now nothing is set on app entry only
when you actually start to navigate. 

I probably should 



--- In [email protected], "Tim Hoff" <[EMAIL PROTECTED]> wrote:
>
> 
> If you want to turn it off completely, there is a compiler setting.  Go
> to project --> properties --> Flex Compiler.  Then uncheck the "Enable
> integration with browser navigation" option.  This should disable the
> forward/back browser buttons from interacting with the swf.  If you only
> want to turn it off for certain navigation components, you're correct,
> you'll need to use:
> 
> <mx:ViewStack historyManagementEnabled="false"/>
> 
> -TH
> 
> --- In [email protected], "flexaustin" <flexaustin@> wrote:
> >
> > Is it possible to shutoff or browserManager for certain components or
> > for the entire application?
> >
> > So after you do the following:
> >
> > browserManager = BrowserManager.getInstance();
> > browserManager.init("", "Welcome");
> > // browserUrlChange just gets the
> > fragment on startup
> > browserUrlChange();
> >
> > Can you now shut off or de-init the browserManager instance for
> > certain components or the entire app? Or can you put a setting in
> > your children components to not notify the browserManager?
> >
> > I know you can do historyManagementEnabled="false" for certain
> > navigator components, but since historyManagementEnabled is set to
> > false by browserManager and I set it manually in the application tag I
> > know its off.
> >
> > The problem I am having is that I have custom component that contains
> > several child components that go very deep. So when I navigate in my
> > component and all the children change IE7 makes several hundred
> > clicking sounds for change of each child so it clicks for about 3
> > mintues each time you navigate.
> >
> > I know I can shut off the clicking sound in my windows settings, but I
> > don't want all my users to have to do this.
> >
>


Reply via email to