On Mon, Mar 21, 2005 at 05:45:24PM +1100, Richard wrote:

> than the icon code you use. Don't know why. Karsten or someone alluded in a 
> previous post to the fact that wxPython seems to be very touchy around all 
> this bitmap/icon stuff.
I did.

> Certainly I've found in practice when creating 
> icons/bitmaps etc that even an apparently innocent bitmap or icon crashes the 
> system, one can re-create it in apparently the same manner and it dosn't.
Yes. That's what I saw, too.

> I've temporarily hardcoded my file with a little house picture, but the code 
> under it should be generic enough to use instead of the icon code.
> 
>       img = wx.Image 
> ('/home/richard/gnumed/gnumed/client/bitmaps/home_path3232.png', 
> wx.BITMAP_TYPE_ANY)
apparently it's 32x32


> ==============================================
>                       bmp = wx.BitmapFromImage (img)
>                       imagelist.Add (bmp)
You could change this to include the bitmap size ...

>                       self.nb.AssignImageList (imagelist)
> ==============================================
...

> [PANIC] (gnumed.py:[EMAIL PROTECTED]): exception value: C++ assertion 
> "(bitmap.GetWidth() == m_width && bitmap.GetHeight() == m_height) || (m_width 
> == 0 && m_height == 0)" failed in ../src/generic/imaglist.cpp(81): invalid 
> bitmap size in wxImageList: this might work on this platform but definitely 
> won't under Windows.
... because apparently wxPython wants that.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel

Reply via email to