Bugzilla – Bug 1236
alarm clock time entry a little wonky
Last modified: 2008-12-15 13:06:26 UTC
couple of examples: - when your time is 12h and the hour is a single digit, when you go in to set alarm time it starts on the 2nd digit, so you have to press left to enter a 1 for 10+hrs - when you enter a digit and let it sit there for a sec, the text entry skips the next digit and you have to go back (like you enter 1 for 1:00, the cursor skips to the second 0) - entering 1 while on the am/pm field goes for PM, 2 goes for AM... seems like it should be the other way around
- easy to change starting cursor position. This does mean an extra press right if the adjustment is only minutes. scrolling works on both 0 and 1 as a pair regardless of column. - this is also easy to turn off, but it is a replication of the same nextchar timing that is used in the text entry. As such, it is a server pref, 'displaytexttimeout' - well, it was intended to be 1 = PM, 0 = AM, since this is a direct match to the math used to convert to the time value ($p * 12 * 60 * 60). I can fix this to ONLY the two digits instead of a repeating pattern (even for AM, odd for PM), or could also fix it to 1=AM 2=PM and ignore all others if that is preferred.
Created attachment 598 [details] first two changes and awaiting feeedback for the 3rd issue. This can be copied to SQN when completed as well if needed. The first and third item will affect all modules making use of INPUT.Time. the second is dependant on the caller.
Dean, was change 4340 intended as a fix for this? was it also intended that each number scroll discreetly? ie, 11->10->19...
Yes, that change was for this bug, and after trying every possible way I settled on individual digit settings to make navigation consistent. Sorry for the thrashing back and forth on this. Both kevins: are you good with these changes? (Marking as fixed, reopen or file new bugs as you see fit.)
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.