|
yeah, i've had people complain about this with GnomeWorks. likely we both use lots of frames/children to organize our ui's so we're both being hit by it.
the problem, as best as i can tell, relates to the 128 frame level boundry. the way the ui works, frames with higher levels are "in front" of other frames. as frames jostle in the stack, they slowly creep up in frame level. the client will occasionally reshuffle the stack (can't remember exactly what forces this to happen). what appears to be happening is the reshuffle fails to order the child frames properly when crossing the 128 frame level boundry. you'll end up with children on lower frames than the parents and so they fail to pick up user interaction.
i've posted about this on the official forums but got nowhere.
your best bet is to try to detect the issue and force all your children frames to be the correct frame level by hand.
|