Hello all!
(environment: Python 2.5.1, wxPython 2.8.7.1, Windows XP SP3)
I’ve been trying to use the FileBrowseButtonWithHistory (henceforth, FBBWH). It looks great - convenient, nice formatting, etc… but it doesn’t generate the events I was expecting, so my callbacks don’t happen.
Looking at the source, I find this comment:
changeCallback – as for FileBrowseButton, but with a work-around for win32 systems which don’t appear to create wx.EVT_COMBOBOX events properly. There is a (slight) chance that this work-around will cause some systems to create two events for each Combobox selection. If you discover this condition, please report it!"
OK, I thought, so someone else has been here before me. But why does it still not work?
Only today did I take a closer look and find that the work-around is on lines 315 to 333 - but someone had bypassed it:
if False:
#if wx.Platform == “WXMSW”:
I commented the “if False” and un-commented the “if wx.Platform…”, and it now works properly.
My questions:
-
why was this workaround removed? Has it, indeed, caused problems on some systems?
-
is there a “clean” way to propagate this change to my users, or should I just edit the file on their machines? (so far, my installed base is small enough that that’s possible…)
-
what’s the plan for future wxPython releases - if I or my users update, will I need to do this again?
-
I realize I could simply make a fork of FBBWH and package it with my
app… that seems wrong, somehow. Maybe I’m wrong, though. Let me
know!
Thanks!