[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi] wx-2.9.2: "bug in wxDatePickerCtrl: m_date not in sync"

From: Greg Chicares
Subject: [lmi] wx-2.9.2: "bug in wxDatePickerCtrl: m_date not in sync"
Date: Wed, 15 Jun 2011 21:41:21 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20110414 Thunderbird/3.1.10

I've built this tarball:
and compiled the 'skeleton' trunk (using HEAD, modified a few minutes ago):
Now when I run
  /opt/lmi/skeleton/bin[0]$./skeleton.exe --unit_test
the diagnostic messagebox copied below appears; I select "No", and the
program crashes. It appears that the failing unit test attempted to set the
value in a wxDatePickerCtrl to one day past its upper limit; the applicable
code in skeleton/mvc_test.cpp would be:

    // Born one day after as-of date, which is forbidden. There is a
    // subtle difference between datepicker and spin controls, at
    // least for msw: an attempt to set a value outside the permitted
    // range is simply ignored for a datepicker (it keeps its old
    // value), but is respected to the extent possible for a spin
    // control (its value is set to whichever limit is closer to the
    // requested new value).

    LMI_YIELD(2, "Try to set birthdate to 19560114, one day past the upper 

I'm not absolutely certain that lmi would ever attempt such an operation, but
I can't easily rule it out either. With wx-2.9.0, all these unit tests passed.
Is this a wx anomaly that should be fixed?

wxWidgets Debug Alert
../src/msw/datectrl.cpp(218): assert "m_date.IsValid() == dt.IsValid() && 
(!dt.IsValid() || dt == m_date)" failed in GetValue(): bug in wxDatePickerCtrl: 
m_date not in sync
Do you want to stop the program?
You can also choose [Cancel] to suppress further warnings.
Yes   No   Cancel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]