> I'm not sure. Look in the archives of wx-dev and/or wx-users. It's
been
> brought up and discussed before.
>Unfortunately, I've not been able to find specific references, except for
something about broken *pixmaps* themes, not Raleigh...
http://lists.wxwindows.org/pipermail/wx-dev/2002-April/019645.html
Anyway, looking at the wxWindows sources of both v2.3.2 and v2.3.3 I found
something interesting:
...
So, 2.3.2 checks contains a typo in the macro name, which should be
DISABLE_STYLE_IF_BROKEN_THEME: this is the reason why in 2.3.2 I get no
warning about broken themes, but surprisingly this is also the reason
why 2.3.2 works and 2.3.3 doesn't!!! So my (possibly wrong) conclusion
is that the code which checks if the current gtk theme is buggy is buggy
itself, as it detects also good themes like my beloved Raleigh. As I'm
absolutely *not* a wxWindows or GTK guru, I'm not sure if this is true,
so I report it here (even if the right place should be wxWindows-dev,
but I don't follow that list - sorry), in the hope that someone could
confirm or correct my guess.
It appears to be so, even according to the message linked to above. But I
really don't know enough in this area to comment on if it is still the Right
Thing to do or not. Please ask about it on wx-dev.
ยทยทยท
----- Original Message -----
From: "Alberto Griggio" <albgrig@tiscalinet.it>
To: <wxpython-users@lists.wxwindows.org>
Sent: Thursday, August 29, 2002 1:49 PM
Subject: Re: [wxPython] please help: strange behaviour of wxListCtrl
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!