[Tutor] wxPython parent classes

[Mark Weil]

wx.Panel provides better cross-platform reliability, so it's fairly standard
practice to go with a Panel in a Frame, and place the buttons, etc. on the
panel.



On Tue, Apr 19, 2011 at 11:59 AM, Eric Stevens <element.effect at gmail.com>wrote:

> I've been noticing that in all the example codes I have seen, when someone
> creates container, x,  inside of a frame or other container class, y, they
> always seem to create an instance of wx.Panel first and then use that
> instance as the parent class of container x. I have been just placing 'self'
> in there, however, letting the class I am creating (whether it be a wx.Frame
> subclass, wx.ScrolledWindow subclass, etc) be the parent class of any other
> wx.Window class I instantiate inside that class. Is one way better than the
> other, and if so, why? Thanks.
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> To unsubscribe or change subscription options:
> http://mail.python.org/mailman/listinfo/tutor
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tutor/attachments/20110419/a023ec40/attachment.html>