In trying to understand nested windows/panels and nested sizers, I
stumbled across the strange fact that my test code works the same
whether or not I have commented out the import of wxFlexGridSizer.
from wxPython.wx import *
##from wxPython.lib.grids import wxFlexGridSizer
Is the second line necessary? If not, why not? I'm sure I will have
lots of other questions about nesting sizers, but this one just has
my curiosity up.
···
=====
Donnal Walter
Arkansas Children's Hospital
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
In trying to understand nested windows/panels and nested sizers, I
stumbled across the strange fact that my test code works the same
whether or not I have commented out the import of wxFlexGridSizer.
from wxPython.wx import *
##from wxPython.lib.grids import wxFlexGridSizer
Is the second line necessary? If not, why not? I'm sure I will have
lots of other questions about nesting sizers, but this one just has
my curiosity up.
The wxFlexGridSizer class was originally implemented in Python, and then was
later ported to C++ and put in the main wxWindows library. At that time I
put Python wrappers around it like all the rest and so that version is now
imported from wxPython.wx. I left wxPython.lib.grids in the distribution
mainly as an example of how to implement a custom sizer, and also with the
hope that somebody would add column and row spanning capabilities to it.
<hint, hint>
···
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!