I see in a email of yours dated Wed
Nov 8 14:39:33 PST 2006 that this bug should have been already fixed in
version 2.7.2 My problem is that I get it now, as you can see from the
message here below with version 2.8.8.1, and it is unusual because until yesterday wx.DatePickerCtrl ran properly. My OS, if this is relevant, is Windows XP Home.
What can I do? Thanks in advance.
C:/Python25/pythonw.exe -u “C:/Python_programs/Titoli/Titoli.py”
Traceback (most recent call last):
File “C:\Python25\lib\site-packages\rb\frames\rbbaseframe.py”, line 586, in OnFillGrid
self.FillGrid()
File “C:\Python_programs\Titoli\movimenti.py”, line 435, in FillGrid
prep = self.PrepareFillGrid()
File “C:\Python_programs\Titoli\movimenti.py”, line 302, in PrepareFillGrid
d.CASTDate(self.dtp.GetValue())
File “C:\Python25\Lib\site-packages\wx-2.8-msw-ansi\wx_controls.py”, line 6415, in GetValue
return controls.DatePickerCtrlBase_GetValue(*args, **kwargs)
wx._core.PyAssertionError:
C++ assertion “m_date.IsValid() == dt.IsValid() &&
(!dt.IsValid() || dt == m_date)” failed at …\src\msw\datectrl.cpp(278) in wxDatePickerCtrl::GetValue(): bug in wxDatePickerCtrl: m_date not in sync
I can add that in a different frame, in the same program, wx.DatePickerCtrl created with the same paramters works perfectly.
I see in a email of yours dated Wed Nov 8 14:39:33 PST 2006 that this bug should have been already fixed in version 2.7.2 My problem is that I get it now, as you can see from the message here below with version 2.8.8.1 <http://2.8.8.1/>, and it is unusual because until yesterday wx.DatePickerCtrl ran properly. My OS, if this is relevant, is Windows XP Home.
What can I do? Thanks in advance.
C:/Python25/pythonw.exe -u "C:/Python_programs/Titoli/Titoli.py"
Traceback (most recent call last):
File "C:\Python25\lib\site-packages\rb\frames\rbbaseframe.py", line 586, in OnFillGrid
self.FillGrid()
File "C:\Python_programs\Titoli\movimenti.py", line 435, in FillGrid
prep = self.PrepareFillGrid()
File "C:\Python_programs\Titoli\movimenti.py", line 302, in PrepareFillGrid
d.CASTDate(self.dtp.GetValue())
File "C:\Python25\Lib\site-packages\wx-2.8-msw-ansi\wx\_controls.py", line 6415, in GetValue
return _controls_.DatePickerCtrlBase_GetValue(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "m_date.IsValid() == dt.IsValid() && (!dt.IsValid() || dt == m_date)" failed at ..\..\src\msw\datectrl.cpp(278) in wxDatePickerCtrl::GetValue(): bug in wxDatePickerCtrl: m_date not in sync
I can add that in a different frame, in the same program, wx.DatePickerCtrl created with the same paramters works perfectly.
Try to find what is different between the two situations and create a small runnable sample that shows the problem.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I realize this is not much of a compass, but the problem does not arise if no specific range is assigned to the wx.DatePickerCtrl.
And even when the range is assigned, if the control’s value is not read immediately but the user manually changes and then resets it to its former apparent worth, the problem does not arise either.
BTW I do not understand what should be in sync with what. Maybe I assigned an impossible value for the range?
I see in a email of yours dated Wed Nov 8 14:39:33 PST 2006 that this bug should have been already fixed in version 2.7.2 My problem is that I get it now, as you can see from the message here below with version 2.8.8.1 <http://2.8.8.1/>, and it is unusual because until yesterday wx.DatePickerCtrl ran properly. My OS, if this is relevant, is Windows XP Home.
wx._core.PyAssertionError: C++ assertion “m_date.IsValid() == dt.IsValid() && (!dt.IsValid() || dt == m_date)” failed at …..\src\msw\datectrl.cpp(278) in wxDatePickerCtrl::GetValue(): bug in wxDatePickerCtrl: m_date not in sync
I can add that in a different frame, in the same program, wx.DatePickerCtrl created with the same paramters works perfectly.
Try to find what is different between the two situations and create a small runnable sample that shows the problem.
Following to my message of this evening, I tried to write a small runnable sample. You can find it here attached but, sorry, it does not show the problem. And the original application, where it did, is too long and complex. Have you any idea for narrowing the target?
I realize this is not much of a compass, but the problem does not arise if no specific range is assigned to the wx.DatePickerCtrl.
And even when the range is assigned, if the control’s value is not read immediately but the user manually changes and then resets it to its former apparent worth, the problem does not arise either.
BTW I do not understand what should be in sync with what. Maybe I assigned an impossible value for the range?
I see in a email of yours dated Wed Nov 8 14:39:33 PST 2006 that this bug should have been already fixed in version 2.7.2 My problem is that I get it now, as you can see from the message here below with version 2.8.8.1 <http://2.8.8.1/>, and it is unusual because until yesterday wx.DatePickerCtrl ran properly. My OS, if this is relevant, is Windows XP Home.
wx._core.PyAssertionError: C++ assertion “m_date.IsValid() == dt.IsValid() && (!dt.IsValid() || dt == m_date)” failed at …..\src\msw\datectrl.cpp(278) in wxDatePickerCtrl::GetValue(): bug in wxDatePickerCtrl: m_date not in sync
I can add that in a different frame, in the same program, wx.DatePickerCtrl created with the same paramters works perfectly.
Try to find what is different between the two situations and create a small runnable sample that shows the problem.
Following to my message of this evening, I tried to write a small runnable sample. You can find it here attached but, sorry, it does not show the problem. And the original application, where it did, is too long and complex. Have you any idea for narrowing the target?
I realize this is not much of a compass, but the problem does not arise if no specific range is assigned to the wx.DatePickerCtrl.
And even when the range is assigned, if the control's value is not read immediately but the user manually changes and then resets it to its former apparent worth, the problem does not arise either.
So should I be able to see this in the sample you sent? (I don't.) Do I need to do anything special to be able to reproduce this?
BTW I do not understand what should be in sync with what. Maybe I assigned an impossible value for the range?
The sync error message refers to two copies of the value that are used in the implementation.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Robin wrote:
So should I be able to see this in the sample you sent? (I don’t.) Do
I need to do anything special to be able to reproduce this?
I hoped you could find some cue in your memory from the former bug resolutions. At this point, since I don’t want to give up, I’ll have to apply Michelangelo recipe for sculpture, namely:
Take a marble block, and then pick off all useless stone.
I’ll try to reduce to a reasonable size my application, keeping the error. But this takes time, so long
I realize this is not much of a compass, but the problem does not arise if no specific range is assigned to the wx.DatePickerCtrl.
And even when the range is assigned, if the control’s value is not read immediately but the user manually changes and then resets it to its former apparent worth, the problem does not arise either.
So should I be able to see this in the sample you sent? (I don’t.) Do I need to do anything special to be able to reproduce this?
BTW I do not understand what should be in sync with what. Maybe I assigned an impossible value for the range?
The sync error message refers to two copies of the value that are used in the implementation.
