As any newbie I'll start with a problem:
I have this problem using the global coordinates.
I have a component (component X) that's nested into another, and the latter as well nested into another one.
i generate these "component X" so i can have one or three or how many i want on the same level. I generate them at runtime.
Everything works perfect so far, but when i generate a "component X" when the main app is in scroll mode, the global coordinates transformation seems to not work anymore. From what I noticed the (0,0) is not the Application's upper left corner, but the visible screen upper left corner at that given moment. So if a component appears with its reference point somewhere above the visible area it gets negative coordinates. Shouldn't 0,0 be in the upper left corner of the app's stage space? I use localToGlobal to convert the "component X"s local coords to the global coords. I'm pretty sure i do it right, because when the app is not scrolled, they are OK and they have the expected coords.
It makes no sense. Anybody had this same problem?
What's really going on with the global coordinates system when the main app scrolls? Can i truly have one fixed reference point?
Thanks in advance
Cristian
--
Cristian Rotundu
====================
__._,_.___
--
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
| Software development tool | Software development | Software development services |
| Home design software | Software development company |
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.
__,_._,___
