I assume that this is a bug, but perhaps not. The new clock templates within the database seem to be mislabeled. I believe that the “duration” is the length of the item in hours, minutes, or seconds. However, the duration box is labeled as a 12 hour clock (e.g 12:00:00 AM). For duration, shouldn’t it be labeled and entries made as the 00:00:00 format?
I’ve also noticed that if you make an entry that creates an overrun warning, the overrun warning does not go away after you remove the offending item.
Also, maybe I’m missing something, but each one hour clock can be assigned to any (or all) hour within the day. If so, why would you define a specific start time to a specific template? Wouldn’t all templates be built to start at 00:00:00 and end at 01:00:00 (an hour length) and then a specific time is automatically assigned when the clocks are assigned?
The dialog uses the standard DateTimePicker component, which apparently follows the Windows locale settings wrt. the time format. Never was aware of it, as we have 24-hour format here in Germany - and actually most part of the world
Same is true for the “fixed time” setting on the Settings tab. As you already noted, fixed times in templates are always relative to the start of the hour, or 00:00:00-based in other words, so the actual hour start time is being added automatically when the template is used to generate a particular hour.
I’m forcing all boxes into 24-hour format now (from v5.2 b2992). Another nice option would be to use the same “smart” edit box that is used for the duration field in the playlist item properties, where you can either enter a time in hh:mm:ss format, or the number of seconds as a number. I will consider this.
Not really able to reproce this. Can you please post two screenshots (one before, one after) to illustrate the issue? Thanks.
Excellent! Yes, the 24-hour clock make sense. It was strange entering a duration of 2 minutes as 12:02:00 AM ;D ;D
As for recreating the issue, I’ve having problems doing so myself now. I’m wondering whether the 12-hour clock issue was confusing me and operator issue was the true issue. I’m still working on the clocks, so if it happens again, I’ll report it with screen shots. Thank you!
