[wx-dev] cvs wxString changes.

[Vadim Zeitlin]

On Mon, 02 Apr 2007 18:15:23 +0200 Gunnar Roth <gunnar.roth at gmx.de> wrote:

GR> the wxstring changes in cvs again break my app.

 I'm not sure if you're aware but there are major changes happening in
wxWidgets right now. It's probably not a good idea to follow the cvs right
now if you're not interested in wxWidgets development (as opposed to
development of your program). And if/when you do update, please make sure
to read docs/changes.txt and especially the section titled "INCOMPATIBLE
CHANGES SINCE 2.8.x" which contains an item for the problem you mention
below.

GR> the line:
GR>         return wxGetApp().Prefs.bDisplayEmptyPlaylistColumnAsUnkown == 
GR> true ? _( "<unknown>" ):wxEmptyString;
GR> yields the error: error: operands to ?: have different types

 Yes, we didn't find any way to make this work.

GR> but  when i recommended to change wxListCtrl 's signature (some years ago)
GR> virtual wxListItemAttr *OnGetItemAttr(long item) const;
GR> to
GR> virtual const wxListItemAttr *OnGetItemAttr(long item) const; ( to not 
GR> be forced to const cast internal member access)
GR> it was said that would break to compile for too many users.

 And also wasn't necessary, strictly speaking. But the incompatibility
introduced by wxString changes to expressions involving operator?: couldn't
be avoided unfortunately.

 Regards,
VZ