[wxPython] Some issues with wxGTK vs wxWin32: wxFrame and wxMiniFrame.

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[wxPython] Some issues with wxGTK vs wxWin32: wxFrame and wxMiniFrame.

Chris Davs
I think I've found some bugs or variations in the wxGTK vs. the win32 version.  I'm hoping someone can help out or test my theory.  In my application, I'm making some new frame (wxMiniFrame) windows appear that contain only  a grid.  They act like modeless dialogs or dialog bars.  I coded it on windows and everything worked find, when I ran it on my Linux machine (redhat 6.1, x386) I got some bad results.

1) when the new frame was created I couldn't edit the grid.  I could select the individual cells but the keyboard would not work.  Typing neither added letters or deleted them.  To solve this problem I decided to use a standard frame (wxFrame).  It fixed the grid problem and I could edit cells, but it created a new problem.

2) The OnCloseWindow wouldn't fire, and the window couldn't be closed.  I also notice that after I provoke a new frame window, I couldn't close the main application frame window.  I could close the windows with an menu or button, but the OnCloseWindow events do not fire.   I check the demo, and I found that I couldn't close the wxFrame demo as well. (I could close the main application frame though).  So I don't think it's just my problem, it could be a bug.

I hope some can help,  I prefer  using the wxMiniFrame with a grid, but I'll settle for a wxFrame with a grid that closes.

-- 
Chris Davis
[hidden email]
www.rpgarchive.com
ICQ#40840786
 
Reply | Threaded
Open this post in threaded view
|

Re: [wxPython] Some issues with wxGTK vs wxWin32: wxFrame and wxMiniFrame.

Robin Dunn

1) when the new frame was created I couldn't edit the grid.  I could select the individual cells but the keyboard would not work.  Typing neither added letters or deleted them.  To solve this problem I decided to use a standard frame (wxFrame).  It fixed the grid problem and I could edit cells, but it created a new problem.

 
Did you try setting the focus to the grid window?  wxMiniFrame may not do that automatically like wxFrame does. 
 

2) The OnCloseWindow wouldn't fire, and the window couldn't be closed.  I also notice that after I provoke a new frame window, I couldn't close the main application frame window.  I could close the windows with an menu or button, but the OnCloseWindow events do not fire.   I check the demo, and I found that I couldn't close the wxFrame demo as well. (I could close the main application frame though).  So I don't think it's just my problem, it could be a bug.

This is a known issue but I am still not sure where the fault lies, in wxGTK or in the wxPython wrappers...
 
--
Robin Dunn
Software Craftsman
[hidden email]
http://AllDunn.com/robin/
http://AllDunn.com/wxPython/  Check it out!
 
Reply | Threaded
Open this post in threaded view
|

[wxPython] Threads

Gary Greyling-2
In reply to this post by Chris Davs
Has anybody here got a short exaple (other than th one in the demo).
--
Gary Greyling
Electric Genetics

_______________________________________________
wxPython-users maillist  -  [hidden email]
http://starship.python.net/mailman/listinfo/wxpython-users