Garage Clock Formatting Error

[Fireholder1]

Hiya, Aslain. Just a heads up that time is not displaying properly. Instead of '12:mm' showing for 12pm, it's displaying '00:mm' (mm = 2-digit minutes).

The clock.xc file has '{{H%02d}}' for the hour formatting. I don't know enough of programming to tell this to display 12 instead of 00.
Got a quick idea so I can fix this myself?


Screenshot:

[Aslain]

{{H....}} is correct according to the manual: 

 

    // Macros available (case sensitive):

    // Доступные макросы (чувствительны к регистру):

    //

    // {{Y}}     - full year (4 digits)       / год (4 цифры)

    // {{MMM}}   - full month name (January)  / Полное название месяца (Январь)

    // {{MM}}    - short month name (Jan)     / Укороченное название месяца (Янв)

    // {{M}}     - month number (1-12)        / номер месяца в году (1-12)

    // {{D}}     - day number (1-31)          / Номер дня в месяце (1-31)

    // {{WW}}    - full weekday name (Monday) / Полное название дня недели (Понедельник)

    // {{W}}     - short weekday name (Mon)   / Укороченное название дня недели (Пон)

    // {{h}}     - hour                       / часы

    // {{m}}     - minute                     / минуты

    // {{s}}     - second                     / секунды

    // {{H}}     - hour in 12-hour format     / часы в 12-часовом формате

    // {{AM|PM}} - AM/PM                      / AM/PM

 

I will check after 00:00 how it displays to me.

[Fireholder1]

It's now 1:08pm (Eastern Daylight Time) here, and clock shows '01'. It's only during the noon hour that it displayed '00'.

[Fireholder1]

Set my system time back to 12pm hour, and removed the two-digit integer (%02d), but this didn't help. Resulted in a single '0' displaying for hour. :/

[Aslain]

No this %02d is needed to display two digit number. Like I said the macro is fine, I think it's a bug in XVM.

[Fireholder1]

Should I report it to modXVM.com?

[Aslain]

I asked there, will let you know if they reply me

[Fireholder1]

Thank you very much.

[Aslain]

I have been listened and the issue suppose to be fixed in latest XVM for 9.5 CT, but only there, so in 9.4 you have to live with this for now.