Paul Wiseman
2014-09-22 15:39:36 UTC
I noticed a bit of odd behaviour when upgrading to wxPython 3.0.1.1
with the wx.lib.masked.TimeCtrl.
Namely 3 things,
- Using colon / tab to change the selection did weird things - to
recreate type '11:' in the timectrl __name__ __main__ demo then begin
typing again.
- Clicking or moving the cursor to a different field, then
incrementing with the spin control or arrow keys incremented where the
cursor used to be
- 24hr format was always being used for me, despite passing False to
the constructor.
I took a look at the issues and created patches for the 3 bugs which
I've attached.
Whats the normal process of getting these reviewed / applied? Should I
make a ticket on wxwidgets tracker?
Thanks!
Paul
with the wx.lib.masked.TimeCtrl.
Namely 3 things,
- Using colon / tab to change the selection did weird things - to
recreate type '11:' in the timectrl __name__ __main__ demo then begin
typing again.
- Clicking or moving the cursor to a different field, then
incrementing with the spin control or arrow keys incremented where the
cursor used to be
- 24hr format was always being used for me, despite passing False to
the constructor.
I took a look at the issues and created patches for the 3 bugs which
I've attached.
Whats the normal process of getting these reviewed / applied? Should I
make a ticket on wxwidgets tracker?
Thanks!
Paul
--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.