wxPython 3.0: TimeCtrl generates wxPyDeprecationWarning: Accessing deprecated property.

wxPython Users
1

To reproduce:

  1. Start the wxPython demo.
  2. Select the TimeCtrl demo.
  3. Click in the “24-hour format” field and press “:” (semicolon).

Warning shown on screen:

C:\Python27\lib\site-packages\wx-3.0-msw\wx\lib\masked\timectrl.py:1209: wxPyDeprecationWarning: Accessing deprecated property.

event.m_shiftDown = False

This does not seem to cause harm, but some of my users have pointed this out in my app log.

Is it harmless? Is there a fix?

Thanks.

2

This message prompted me to look at the timectrl in Phoenix and
noted it still has the same problem - and a few others, e.g. all
values are flagged as invalid.
The fix for the above in Phoenix, which should be the same for your
version is to change from:
event.m_shiftDown = False
To:
event.shiftDown = False
Werner

···

Hi Edward,

  On 6/24/2014 18:46, Edward Sitarski wrote:

To reproduce:

  1. Start the wxPython demo.
  2. Select the TimeCtrl demo.
  3.           Click in the "24-hour format" field and press ":"

(semicolon).

Warning shown on screen:

        C:\Python27\lib\site-packages\wx-3.0-msw\wx\lib\masked\timectrl.py:1209:

wxPyDeprecationWarning: Accessing deprecated property.

event.m_shiftDown = False

      This does not *seem* to cause harm, but some of my users

have pointed this out in my app log.

Is it harmless? Is there a fix?

:frowning:

3

That fixed it. Thanks.
I wonder if clearing the flag is really necessary - everything seemed to still work.

···

On Wednesday, June 25, 2014 10:12:17 AM UTC-4, werner wrote:

Hi Edward,

  On 6/24/2014 18:46, Edward Sitarski wrote:

To reproduce:

  1. Start the wxPython demo.
  2. Select the TimeCtrl demo.
  3.           Click in the "24-hour format" field and press ":"

(semicolon).

Warning shown on screen:

C:\Python27\lib\site-packages\wx-3.0-msw\wx\lib\masked\ timectrl.py:1209:
wxPyDeprecationWarning: Accessing deprecated property.

event.m_shiftDown = False

      This does not *seem* to cause harm, but some of my users

have pointed this out in my app log.

Is it harmless? Is there a fix?

This message prompted me to look at the timectrl in Phoenix and

noted it still has the same problem - and a few others, e.g. all
values are flagged as invalid :frowning:
.

The fix for the above in Phoenix, which should be the same for your

version is to change from:

event.m_shiftDown = False



To:



event.shiftDown = False



Werner
4

Hi Edward,

That fixed it. Thanks.

Great.

I wonder if clearing the flag is really necessary - everything seemed to still work.

A deprecation warning only informs you that in a future version m_shiftDown will no longer be there and then you would get an error.

My guess is that, Will Sadkin who wrote this control, clears it to change how the char is evaluated, in this case ":" is acting like if you pressed tab.

Werner

···

On 6/25/2014 16:44, Edward Sitarski wrote: