I have that set already and it seems to have no impact on this. I think thats becuase the SystemManager is capturing the MouseDown at SystemManager level so it sees the mouse down event which is not really effected by mouseFocusEnabled setting on the button.
Once it sees the mouse down it runs the activate/deactivate code regardless of any focus enabled prop. --- In [email protected], Alex Harui <aha...@...> wrote: > > mouseFocusEnabled=false > > 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 reflexactions > Sent: Thursday, September 24, 2009 8:47 AM > To: [email protected] > Subject: [flexcoders] Re: How to stop a button click from changing focus > > > > Yes I want to be able to click in the main form because that is where the > button is, this is why using modal or disabling the main app won't work. > > If it is easier to understand think of a toolbar that lives in the main form > with several non-modal popup windows. Clicking the toolbar will do something > to the active popup. > > So when you click a button in the toolbar I dont want it to remove focus from > the active popup, becuase otherwise by the time the button's click fires > focus has been moved to the main app. > > So far a hack that works is to have my own mouseDown handler that runs ahead > of the SystemManager and stops the event propagating if the target is my > button but I am not currently sure of the consequences of this. > > --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, Tom > McNeer <tmcneer@> wrote: > > > > First question would be: do you *want* them to be able to click in the main > > form? > > > > If not, you could simply set the "modal" property of the popup to "true" > > when you create it. > > > > > > > > > > -- > > Thanks, > > > > Tom > > > > Tom McNeer > > MediumCool > > http://www.mediumcool.com > > 1735 Johnson Road NE > > Atlanta, GA 30306 > > 404.589.0560 > > >
