Hello all,
I just installed the lastest release for Mac OS X, and am receiving disturbing messages like:
'BoxSizer' object has attribute 'GetItem'... doing a dir() on the object in question (a wxBoxSizer) shows that in fact GetItem is not there. Same for FlexGridSizer in another test I ran. The wxWidgets docs still show GetItem() as a valid method on the Sizer class, but I'm not seeing in wxPython. Any thoughts?
Thanks!
Brian Brown
Brian Brown wrote:
Hello all,
I just installed the lastest release for Mac OS X, and am receiving disturbing messages like:
'BoxSizer' object has attribute 'GetItem'... doing a dir() on the object in question (a wxBoxSizer) shows that in fact GetItem is not there. Same for FlexGridSizer in another test I ran. The wxWidgets docs still show GetItem() as a valid method on the Sizer class, but I'm not seeing in wxPython. Any thoughts?
Are you sure you're using the latest version?
$ pydoc wx.BoxSizer.GetItem
Help on method GetItem in wx.BoxSizer:
wx.BoxSizer.GetItem = GetItem(*args, **kwargs) unbound wx._core.BoxSizer method
GetItem(self, item) -> wx.SizerItem
Returns the `wx.SizerItem` which holds the *item* given. The *item*
parameter can be either a window, a sizer, or the zero-based index of
the item to be detached.
$ pythonw -c "import wx; print wx.VERSION"
(2, 6, 1, 0, '')
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Hmm, this is a fresh install of Tiger, and the first version of wx I put on here... it seems that Tiger is bundled with 2.5.3.1... I ran the uninstall script, and it didn't find that version, which is install in /usr/lib.
How can I make it use the new version instead of the bundled one?
Brian
On Jun 15, 2005, at 3:22 PM, Robin Dunn wrote:
Brian Brown wrote:
Hello all,
I just installed the lastest release for Mac OS X, and am receiving disturbing messages like:
'BoxSizer' object has attribute 'GetItem'... doing a dir() on the object in question (a wxBoxSizer) shows that in fact GetItem is not there. Same for FlexGridSizer in another test I ran. The wxWidgets docs still show GetItem() as a valid method on the Sizer class, but I'm not seeing in wxPython. Any thoughts?Are you sure you're using the latest version?
$ pydoc wx.BoxSizer.GetItem
Help on method GetItem in wx.BoxSizer:wx.BoxSizer.GetItem = GetItem(*args, **kwargs) unbound wx._core.BoxSizer method
GetItem(self, item) -> wx.SizerItemReturns the `wx.SizerItem` which holds the *item* given. The *item*
parameter can be either a window, a sizer, or the zero-based index of
the item to be detached.$ pythonw -c "import wx; print wx.VERSION"
(2, 6, 1, 0, '')--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Ok, I made it past the install, now the wxPython demo seems to run well.
Whenever I call wx.EmptyBitmap(), I get the following:
File "/Users/brian/Dev/TechGame/framework/proj/skinning/toolkits/wx/frames/frame_splash.py", line 40, in frame_splash
splashBitmap = wx.EmptyBitmap(0,0)
File "//Library/Python/2.3/wx-2.6-mac-unicode/wx/_gdi.py", line 727, in EmptyBitmap
val = _gdi_.new_EmptyBitmap(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "m_hBitmap" failed in ../src/mac/carbon/bitmap.cpp(182): Unable to create GWorld context
However, if I use wx.EmptyBitmap(1,1) it works fine.
We've been using this with many versions of wx.. any idea why this changed? Or is it a bug?
Brian
On Jun 15, 2005, at 3:59 PM, Brian Brown wrote:
Hmm, this is a fresh install of Tiger, and the first version of wx I put on here... it seems that Tiger is bundled with 2.5.3.1... I ran the uninstall script, and it didn't find that version, which is install in /usr/lib.
How can I make it use the new version instead of the bundled one?
Brian
On Jun 15, 2005, at 3:22 PM, Robin Dunn wrote:
Brian Brown wrote:
Hello all,
I just installed the lastest release for Mac OS X, and am receiving disturbing messages like:
'BoxSizer' object has attribute 'GetItem'... doing a dir() on the object in question (a wxBoxSizer) shows that in fact GetItem is not there. Same for FlexGridSizer in another test I ran. The wxWidgets docs still show GetItem() as a valid method on the Sizer class, but I'm not seeing in wxPython. Any thoughts?Are you sure you're using the latest version?
$ pydoc wx.BoxSizer.GetItem
Help on method GetItem in wx.BoxSizer:wx.BoxSizer.GetItem = GetItem(*args, **kwargs) unbound wx._core.BoxSizer method
GetItem(self, item) -> wx.SizerItemReturns the `wx.SizerItem` which holds the *item* given. The *item*
parameter can be either a window, a sizer, or the zero-based index of
the item to be detached.$ pythonw -c "import wx; print wx.VERSION"
(2, 6, 1, 0, '')--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Brian Brown wrote:
Ok, I made it past the install, now the wxPython demo seems to run well.
Whenever I call wx.EmptyBitmap(), I get the following:
File "/Users/brian/Dev/TechGame/framework/proj/skinning/toolkits/ wx/frames/frame_splash.py", line 40, in frame_splash
splashBitmap = wx.EmptyBitmap(0,0)
File "//Library/Python/2.3/wx-2.6-mac-unicode/wx/_gdi.py", line 727, in EmptyBitmap
val = _gdi_.new_EmptyBitmap(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "m_hBitmap" failed in ../src/ mac/carbon/bitmap.cpp(182): Unable to create GWorld contextHowever, if I use wx.EmptyBitmap(1,1) it works fine.
We've been using this with many versions of wx.. any idea why this changed? Or is it a bug?
There were some changes a while back to the native objects that wxMac uses for holding a wxBitmap. Apparently they don't like having a size of (0,0), which makes some sense.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!