D. R. Evans wrote:
I know that, the look and feel is not always exactly the same in the
diffrent OS ...
But, I ask me why don't you change the bitmap with a |SetBitmap(self,
bitmap) ?Thank you for your e-mail.
1. This isn't just a look-and-feel issue, it's a difference in
behaviour. I do expect things to look slightly different on the two
OSes; I didn't expect different behaviour2. I haven't come across the SetBitmap command yet (I only downloaded
wxPython earlier today, and before that had never used it). I figured
that there had to be some way to replace the bitmap in place, but the
obvious command (Replace) did not exist. Indeed, even now that I know
that SetBitmap exists, I can't find the documentation for itThe
wx.Bitmap documentation doesn't mention the function
Look at wx.StaticBitmap. The wx.Bitmap is the image data in a platform dependent structure, the wx.StaticBitmap is the widget that displays it.
Per my recent post, I found a workaround by calling Refresh() explicitly
You probably still have a problem, as I don't think that the sizer's Remove method will destroy the old widget, so it is probably still there underneath the new one. So the best solution would be to use the widget's SetBitmap method to change what is displayed, but keep in mind if you ever want to take widgets out of a sizer the easiest way to do it is to simply destroy the widget. It will remove itself from the sizer on the way to the bit-bucket.
ยทยทยท
On 21/08/07, Geoffroy Culot <geoffroy.culot@gmail.com> wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!