This is not something new, it happens with 2.6 as well.
Whenever I open a frame from a ListCtrl item (i.e via right click menu, or item double click) the Frame appears in the background instead foreground. Linux and Windows don’t have this issue.
Some more details:
With 2.6 I have used the following for opening the new frame:
item left double-click
space key hit
right click menu item
(2) and (3) always opened the frame in background.
(1) worked well only without adding event.Skip().
now that 2.7 can’t catch the left double-click event and I’m forced to use the activate event all three ways don’t work well.
Is it a bug ? or am I doing something wrong (unlikely)?
Have you tried using frame.Raise(), either directly or via wx.CallAfter?
- Josiah
···
"roee88 shlomo" <roee88@gmail.com> wrote:
This is not something new, it happens with 2.6 as well.
Whenever I open a frame from a ListCtrl item (i.e via right click menu, or
item double click) the Frame appears in the background instead foreground.
Linux and Windows don't have this issue.
This is not something new, it happens with 2.6 as well.
Whenever I open a frame from a ListCtrl item (i.e via right click menu, or item double click) the Frame appears in the background instead foreground. Linux and Windows don't have this issue.
What is the parent of the new frame?
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
This is not something new, it happens with 2.6 as well.
Whenever I open a frame from a ListCtrl item (
i.e via right click menu,
or item double click) the Frame appears in the background
instead foreground. Linux and Windows don’t have this issue.
What is the parent of the new frame?
–
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I see the following behavior on Mac OSX 10.4, wxPython 2.6 and 2.7, Python 2.4: if I activate the item with the mouse (double click) the new frame is behind the list. If I activate the item with the keyboard (return) the new frame is before the list. Apparently, the mouse event is sent to the list too, causing it to be raised. There is a simple fix though: