- Status Neu
- Prozent erledigt
- Aufgabentyp Wunsch / Idee
- Kategorie GUI & Server
- zuständig niemand
- Betriebssystem Unbekannt
- Schweregrad niedrig
- betrifft Version 3.3.1
- fällig in Version unbestimmt
-
fällig am
unbestimmt
- Stimmen
- versteckt
FS#5525 - Improvement to entry of cuelist times: accept decimal values
Hi,
I would like to suggest an improvement to the way times are entered in the cuelist.
Currently, if I wanted to enter a time of 5 seconds 300 milliseconds for a wait cue, I would need to enter “5s300ms” which is quite awkward to type because it’s a mixture of numbers and letters. If I try to enter “5.3” this generates an error message “Trigger value not valid”.
Ideally, decimal numbers would be automatically turned into seconds and milliseconds. Eg “10.244” becomes “10s244ms”, and “0.123” becomes “123ms”.
I create a lot of time-based cuelists with a large number of ‘wait’ cues and it would be much quicker to be able to enter these values entirely on the numeric keypad rather than having to keep typing ‘s’ and ‘ms’ to denote seconds and milliseconds.
This should probably be consistent wherever times are entered - so the fade and delay values should also work the same way. (Currently fade times default to milliseconds but cue times default to seconds which is inconsistent.)
well you don't have to enter this mixture of numbers and letters. There is already an automatic conversion. It is just different than you thought: At least in some of the rows you can enter the time in milliseconds.Then it is automatically converted. So e.g. if you enter 5300 it is converted to 5s300ms
Hi JPK,
That's only true for the fade and delay values.
Using your example above, if you enter 5300 in a cuelist trigger value it converts to 1h28m20s (which is 5300 seconds).
So the cuelist trigger value input is in *seconds*. But it doesn't accept numbers with a decimal point, and I think it is logical that if you enter a number such as 1.224, it should interpret that as 1s224ms, rather than saying "Trigger value not valid".
It is actually a known issue that there are differences between fade and delay on the one side and the trigger value on the other side regarding the units. I don't like that either, but currently it is what it is. We will fix that when we rewrite the cuelist control in WPF. Then we will also think about better ways to enter time values for those three values and will make them identical.
However, until then, there are two arguments against a change:
Yes, I agree there's no point implementing things twice, and appreciate this is a hobby project.
I labelled it as a low priority wishlist idea - just something that would be nice to see in a future version to improve ease of use.