Thanks to some various clues here, I got thinking about the
wxSplitterWindow problem a bit and came up with what I believe is a
workable solution. I've posted it to the Wiki here:
Basically, if you capture the size event for the window, you can then
safely know the size of the window, and then do what I wanted to do all
along -- relatively set the sash position in the same way we can weight
wxSizers.
Might break something, but it's a good start.
Jeff Grimmett aka Grimmtooth
"Soylens Viridis Homines Est"
Thanks to some various clues here, I got thinking about the
wxSplitterWindow problem a bit and came up with what I believe is a
workable solution. I've posted it to the Wiki here:
Basically, if you capture the size event for the window, you can then
safely know the size of the window, and then do what I wanted to do all
along -- relatively set the sash position in the same way we can weight
wxSizers.
AS you can see in my other message, this is exactly what I suggest. Good Job!
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
AS you can see in my other message, this is exactly what I suggest.
Good Job!
Yeah, saw that
There are still some issues here. For example, getting it to play nice with
sizers and wx*Sizer.SetSizeHints(frame). No matter what I've tried, I always
end up with a frame that's too small. But as long as I avoid that, sizers
inside window1 and window2 seem to work OK.
