wxPython StaticBitmap behavior changed with/before version 4.2.2?

Question

In the course of buying a new laptop, I've upgraded wxPython to version 4.2.2, and in an otherwise-fine GUI application (including tree, forms, perspectives, ... all provided with wxPython), the placement of StaticBitmap controls on a Panel does not work anymore:

Instead of being laid out in a grid, the bitmaps all start from the origin (0,0), overlapping. The correct position is supplied to StaticBitmap() (as before with the old wxPython version), but seemingly the behavior of StaticBitmap or Panel or ... has changed.

In the documentation, there's the caveat that StaticBitmap is reliable only for small images, and larger images should use GenericStaticBitmap. Is that the point of change and failure?

Any pointers?

EDIT: Forgot to mention: I also checked the wxPython version history and only found "added wrapper to GenericStaticBitmap" (v4.2.1) while searching for "StaticBitmap" - this should not affect the use of StaticBitmap, I think.

I believe you will have to provide an MWE and/or much more information. Are the bitmaps laid out with a sizer? What platform and OS? — Infinity77
– Infinity77, Commented Mar 7 at 21:09

virtualnobi · Accepted Answer · 2025-03-07 21:25:17Z

1

As every so often, a trivial mistake: The position parameters for the origin were not converted to int, but were floating point values. I can't believe the old laptop had a resolution which never resulted in .5 floats, but applying int(...) solves the issue.

Switching to wx.GenericStaticBitmap didn't help, by the way.

answered Mar 7 at 21:25

virtualnobi

1,1902 gold badges12 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Rolf of Saxony Mar 9 at 18:38

Plus 1 for having the cajones to admit the error. The point being that even the error will almost certainly help someone else who has a similar error and didn't check.

virtualnobi Mar 13 at 9:06

:-) Thanks, that was my thinking as well.

Headcrab Apr 4 at 20:43

Probably has nothing to do with the laptops resolution. I remember "suddenly" getting such errors on the same exact hardware as before (the screen, the GPU, everything). Worked before with whatever numerals, I didn't bother explicitly converting to int, because why would I, then I upgraded wxPython and it didn't work anymore. Although, as I remember, I got runtime exceptions, not the program "working" but misbehaving.

Collectives™ on Stack Overflow

wxPython StaticBitmap behavior changed with/before version 4.2.2?

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related