Hi All,
I’m having problems stopping mouse events falling through to a child window.
I have a window module containing a PtButton widget. The button instantiates
a child window which consists of about 70 widgets. Running on an STPC
Client, it takes up to two seconds to instantiate the whole child window
(not acceptable, I need to address this). About half of this time, the
parent window is still displayed, and it is still active to mouse events.
ie, If I click multiple times on the button which opens the child window,
although I only get one instance of the child window, the additional mouse
clicks are received by a button on the child window which happens to be in
the same position as the button on the parent window (make sense??!). I have
tried various combinations of PtCONSUME_EVENTS flags, but this doesn’t
appear to solve the problem. Any Ideas?
Thanks in advance.
Nick Tipping.
Nick Tipping <nick.tipping@virgin.net> wrote:
Running on an STPC
Client, it takes up to two seconds to instantiate the whole child window
(not acceptable, I need to address this).
Well if you are creating the child window with 200 widgets on the
fly, you could create it and realize when the button press
occurs. This would move the delay to startup time.
About half of this time, the
parent window is still displayed, and it is still active to mouse events.
Are you doing something to make the parent dissappear?
ie, If I click multiple times on the button which opens the child window,
although I only get one instance of the child window, the additional mouse
clicks are received by a button on the child window which happens to be in
the same position as the button on the parent window (make sense??!).
This sounds like the parent isn’t really there, but only appears to
be.
Mitchell Schoenbrun --------- maschoen@pobox.com