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
On 15/8/06 09:04, "Sergey Kovalyov" <[EMAIL PROTECTED]> wrote:
Hi All!
I do not need Box container. Only box shape that could change its
background and stroke colors and handle mouse events. Sure, I can use
box itself, but it seems like heavyweight solution. Do I need to
subclass InteractiveObject and override method... Which one method?
Sergey.
__._,_.___
--
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
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
