On Wed, 2012-03-28 at 15:40 +0100, Dave Page wrote:
> On Wed, Mar 28, 2012 at 1:37 PM, zgilboa <zgilboa(at)virginia(dot)edu> wrote:
> > <<
> > << We are really interested to know what kind of issues you'll have with
> > << wxWidgets 2.9. There has been not a lot of checks with this release, so
> > << any issues you find are definitely interesting.
> > *IsEmpty* now has some ambiguity issues: see for instance ldg/ldgServer.cpp
> > my intuition was to change IsEmpty to IsTextEmpty
> > the wxWidgets 2.9 online documentation has a paragraph about it, see:
> > http://docs.wxwidgets.org/trunk/classwx_combo_box.html
> Hmm, looks like that is a change in 2.9.4 (it works OK in 2.9.3). I'm not
> sure I want to go chasing this one yet - it seems like a widespread change
> that will be somewhat hard to find without the compiler throwing errors.
> Better to wait until 2.9.4 is released I think (rather than start
> continuously updating for upcoming versions).
There are already quite a lot of stuff to fix before this one.
In response to
pgadmin-support by date
|Next:||From: Guillaume Lelarge||Date: 2012-03-29 19:44:09|
|Subject: Re: feature request - allow to set option
is_called for setval|
|Previous:||From: Dave Page||Date: 2012-03-28 14:40:05|
|Subject: Re: 1.15 Dev with wxwidgets 2.9.3|