1 person found this helpful
Tree uses masking and virtual renderers so it is probably correct, but not
what you expect.
Container scrolling does have a bug with the stage coordinates. I think you
have to wait for ENTER_FRAME
I have tested the ENTER_FRAME event and indeed when computing stage coordinates using those methods, correct results are returned.
I have a component that it "attaches" itself near another component and my component must be a child of the stage. There problem with using the ENTER_FRAME event is that although it is positioned correctly near the other component, the user can observe with the eye a slight delay. I interpret it as because in the ENTER_FRAME phase the screen is allready in a final drawn state, I just react to a screen "after" draw event and not to a screen "before" draw event, which would give me the posibility to alter it by making my own changes.
I have made a test adding those 20-50 events to be listened and I have observed that the first moment where the computation of the stage coordinates is correct is the ENTER_FRAME event. Unless there are other events I have not listened it seems there is no uniform solution to determine the correct
stage coordinates after a scroll and before the "drawing" to be made on the screen.
Have you other sugestions please?
Thank you for your time,
It's been filed as a bug. I don't know of other solutions.
Thank you for your time and interest.
Because it may be possible for other to have this problem, my solution (an non-uniform one) was for the Container to manually compute the coordinates based on the contentPane's coordinates after UPDATE COMPLETE event and for Tree to add listeners with lower priority on the scrollbars so that the updating the rows to happen before receiving notification.