Hi,
I investigated the issue deeper and it seems the problem is *only* with
one Panel component. Other controls of the main window get key events
properly. So it is very likely some application bug, not Pivot's.
The issue popped up when I introduced that tool window child Frames into
the GUI, so I thought at first it might be caused by them. Now I'm not
so sure. Needs more investigation.
Regards,
Piotr
W dniu 2011-12-04 18:10, Sandro Martini pisze:
Hi Piotr,
are you using sources from latest trunk ? If not, could you try ?
Probably none of us has a case like yours, so could be intetesting to
see if it's a bug (and where) or not.
A great speedup could be an attach with a simple test case ...tomorrow
I should freeze 2.0.1 sources, so have an idea of what is could help
us to see what to do.
Tell me.
Thanks,
Sandro
Il giorno 04/dic/2011 18:01, "Piotr Kołaczkowski"
<[email protected] <mailto:[email protected]>> ha
scritto:
Hi,
My application consists of a Window in which I have several
non-modal Frames open. These Frames serve a role of tool windows,
while the main window contains the working-area of the application.
I noticed, that:
1. one Frame is always active (it has its titlebar highlighted),
even if I click in the area of parent window, and *not* into any
child frame
2. sometimes (?) something (the active Frame?) eats my keyboard
events that should be handled by the parent Window.
Is it possible to have several child Frames, but all inactive (if
the user clicks outside of any Frame, into the area of the parent
Window, only the Window should be active and child frames
deactivated)?
Or how can I make the parent Window receive all the keyboard events?
Or is it a bug?
Regards,
Piotr
--
Piotr Kołaczkowski
Instytut Informatyki, Politechnika Warszawska
Nowowiejska 15/19, 00-665 Warszawa
e-mail: [email protected]
www: http://home.elka.pw.edu.pl/~pkolaczk/
