RE: [wxPython] I may need a MDI reality check
Hi Sam,
I have an example MDI program that uses a sash instead of a splitter to split the main frame horizontally. The sash is then split using a splitter to split the sash vertically. Unfortunately, I’m at home and the code is at work. I’ll post it to the list tomorrow, if you want.
Another problem is that there appears to be a bug in the latest, 2.3.2.* versions of wxWindows that causes an annoying problem in my program. It works fine in version 2.3.1. Details in the follow-up message tomorrow.
Matthew
···
-----Original Message-----
From: Sam Leming [mailto:gibbs05@airmail.net]
Sent: Tuesday, June 04, 2002 3:13 AM
To: wxpython-users@lists.wxwindows.org
Subject: [wxPython] I may need a MDI reality check
Greetings all,
I’ve recently returned to Python programming after over a year of Java exile
and wxPython is completely new to me.
I’d like to write an application that uses a wxMDIParentFrame on one side of
a splitter and several controls on the other. Can a MDI parent frame have
parents in general and a splitter parent in particular? I’m not asking for
how to do this, I just want to know if it’s possible or prudent.
As I’ve said before, I’ve just started with wxPython. I don’t want to get
stuck in a “default behavior tar pit” right from the start. I’ve thrown
together a test app with a wxTextCtrl on the right side of a splitter and a
wxMDIParentFrame on the left. When I drag the splitter sash to the left it
leaves images of the sash behind in the MDI area. Resizing the window
gives me border artifacts in the MDI area. I haven’t been able to create a
MDI child window yet either.
Are these just speed bumps or am I going down the wrong road completely?
I guess plan B would be to make the MDI parent frame the top level and stick
the permanent controls to the side.
TIA,
Sam