Spark wherever I can. While investigating, I found that the component does
work fine in a Spark TitleWindow. There must be some other factor, possibly
related to Parsley, but I'm still working on it.
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
Of Alex Harui
Sent: Thursday, April 29, 2010 12:58 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] TitleWindow Custom Components - A Problem
Are you still using mx components or switching to spark?
On 4/29/10 8:32 AM, Battershall, Jeff jeff.battersh...@dowjones.com wrote:
Hi,
Let me describe the scenario: I'm using Hillen Coren's AutoComplete component
to suggest choices for a user inside of a DataGrid ItemRenderer, which has been
working fine in Flex 3.x for a year. One additional factor - this grid is
popped up as part of a TitleWindow using PopUpManager.
I'm now porting the application to Flex 4 and Parsley. That port is going
great, but the AutoComplete component simply stopped working when part of this
popped up Window. It works fine within the main app.
Has anyone run into similar behavior? I've noticed 'interesting' stuff with
TitleWindows in the past. Any advice appreciated
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
