Bugzilla – Bug 9269
Time format selection with double entries
Last modified: 2009-09-08 09:23:11 UTC
Under Player Settings - Display - Time Format the 24h selection is repeated: 10:06 AM (12h) 10:06 (24h) 10.06 (24h) 10,06 (24h) 10h06 (24h) 10:06 (24h) 10.06 (24h) 10,06 (24h) 10h06 (24h) Seen on SN test and prod
I don't think they are really dupes: q(%H:%M) => 'hh:mm (24h)', q(%H.%M) => 'hh.mm (24h)', q(%H,%M) => 'hh,mm (24h)', q(%Hh%M) => "hh'h'mm (24h)", q(%l:%M %p) => 'h:mm pm (12h)', q(%k:%M) => 'h:mm (24h)', q(%k.%M) => 'h.mm (24h)', q(%k,%M) => 'h,mm (24h)', q(%kh%M) => "h'h'mm (24h)",
Ok, but the texts in the drop-down menu do not reflect this or at least not always. The drop-down uses the actual time to show what the format will look like, so if it is 10:05 there are two identical menus, only if it is three minutes after midnight I get two different entries '0:03 (24h)' and '00:03 (24h)'.
Would you prefer it to display some arbitrary time?
Hmm, good question, I actually like the touch it uses the current time, but as I said that can lead to identical entries. Is there some other standard way to indicate whether the leading '0' is shown or not?
Dean states we should use a fixed AM time (such as 4:20am) instead of using the local time. This will make the differences clear.
let's make it the same as SC and discuss post 7.2/devo
change 4385 - align time selection box with SC 7.2
Created attachment 3905 [details] SC 7.2 Time Selector Box
Created attachment 3906 [details] SN Devo Time Selector (per player)
Looking at the time selector boxes from SC and SN I see a vast difference. Also, on SN they are per player, where on SC they are system wide. Please verify this is expected behavior
James - the difference is that we don't support seconds on SN. Other than that they're the same formats. I copied over the list from SC, ripped out those with seconds. What's left is what you see in SN.
Felix: Do you consider this resovled?
I don't see double entries anymore. So, yes. I'll close the bug then.
This bug has been fixed in the latest release of SqueezeNetwork! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.