Yes, I think subclassing UIComponent and then overridding updateDisplayList() method is the best approach in this case.

On 8/15/06, Samuel D. Colak <[EMAIL PROTECTED]> wrote:

Best to subclass UIComponent and then do the work yourself – it seems heavy handed but its very reliable and by default the property objects are all there – remember if you want to avoid it affecting the layout design, try

IncludeInLayout  = false

You would simply trap all messages to MouseEvent.MOUSE_DOWN using a standard event listener. By doing this you could simply add this object into the parent window without any assertion issues.

Regards
Samuel

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to