Bug #720
closed
launcher clock shows 12pm at 0pm
Added by Hammel over 4 years ago.
Updated 6 months ago.
Description
The digital clock in the launcher is showing the time at noon to be 0:00pm instead of 12:00pm. Probably the same problem as 0:00am but I haven't tested that.
- Priority changed from Normal to Immediate
- Target version changed from 0.5.0 to 3.0 - Corrino
- Severity changed from 03 - Medium to 01 - Critical
- Status changed from New to In Progress
- % Done changed from 0 to 10
I need to reverify this because the code SHOULD work with the format argument %I to strftime(). So I need to set the date manually to 11:59 (am or pm) and then see if it changes to 12 instead of 0.
Oops - wrong launcher. I was looking at PiBox's launcher. Ironman's launcher does time differently in updateClock(). It should probably do things the same way as the PiBox launcher.
- Status changed from In Progress to Rejected
- % Done changed from 10 to 100
This issue is moot since Ironman is switching to the PiBox systems launcher.
Rejecting issue.
Also available in: Atom
PDF
Updated by