Alex, I'm so far along with the workaround, I don't know if I'm going to see it again - hopefully not. My workaround is to display the popup and simply show/hide it without using PopUpManager to remove it. Somehow the removal of the popup combined with FocusManager is producing the behavior.
Jefff ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Wednesday, June 16, 2010 7:49 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] FocusManager Bug in Flex 4 Jeff, What does the call stack look like? On 6/16/10 1:57 PM, "Battershall, Jeff" <jeff.battersh...@dowjones.com> wrote: Alex, Looks like I spoke too soon. When loading one customer and then switching to another, I'm seeing the error again. Getting to the point where I might look to a completely different method of showing and hiding this subform and forget about PopUpAnchor. But it isn't just PopAnchor, its PopUpAnchor + Spark List + virtual layout. Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Wednesday, June 16, 2010 4:16 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] FocusManager Bug in Flex 4 It's definitely a bug. FocusManager should be forgiving. I assume it will get fixed for the next major release. Glad you got around it. FocusManager is expecting children it has seen added to its tree to be on stage when their visibility gets changed. On 6/16/10 10:22 AM, "Battershall, Jeff" <jeff.battersh...@dowjones.com> wrote: Alex, I've worked around this - here's what I was doing and what I discovered: I have a form that has a sub-forum that is popped up using PopUpAnchor. I then could add a new item to the sub form and edit it. Then I would send the main form and subform data to the server using Remoting. But in my case, the newly added item was getting orphaned ano not inserted, and when the returned form contents came back, the itemrenderer that was being used for the new item wasn't there - possibly FocusManager was expecting it to be there. When I fixed the cause of the orphaning, the problem went away. I still feel like shouldn't be happening but for the time being I can move forward. Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Wednesday, June 16, 2010 12:32 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] FocusManager Bug in Flex 4 Unfortunately got deferred because we didn't have a real-world, but simple test case. Do you have one? It seems to be caused by something not being on stage and having visibility flipped. I think one user was binding visible to something that was supposed to evaluate to true, but didn't always because the binding chain wasn't fully created. What does your call stack look like? On 6/16/10 7:45 AM, "Battershall, Jeff" <jeff.battersh...@dowjones.com> wrote: Hi, I too am getting the DisplayObject(form).stage.focus = null error. In my case, I'm using a PopUpAnchor to show and hide a form. Is there a definitive fix for this? Jeff Battershall Application Architect Dow Jones Indexes jeff.battersh...@dowjones.com (609) 520-5637 (p) (484) 477-9900 (c) -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
