Event ID # padding
Posted: Mon Oct 27, 2014 10:39 am
Could we get an option to zero pad the event ID #'s to a specified length?
There's already an option EVENT_IMAGE_DIGITS for the image files, but AFAIK no option to configure event ID's similarly.
Something llke:
EVENT_ID_DIGITS
This would zero pad event ID's the same way image files can be zero padded.
Without this option working with events from the command line can be a bit tricky if you happen to have a collection of events that span across a change in digit length (99, 100) or (999, 1000) and when the ID's roll over back to 1.
If the ID's need to be limited to 5 digits (1...99999, 1, etc) for whatever reason just writing them to the directory structure with the zero padding would help. So the option might be:
EVENT_ID_PADDING=[yes|no]
At least with that you'd have (00001-99999, 00001, etc). Any trickiness to dealing with events in the file system would only happen when the ID's roll over back to 1 and that probably doesn't happen very often for most setups.
There's already an option EVENT_IMAGE_DIGITS for the image files, but AFAIK no option to configure event ID's similarly.
Something llke:
EVENT_ID_DIGITS
This would zero pad event ID's the same way image files can be zero padded.
Without this option working with events from the command line can be a bit tricky if you happen to have a collection of events that span across a change in digit length (99, 100) or (999, 1000) and when the ID's roll over back to 1.
If the ID's need to be limited to 5 digits (1...99999, 1, etc) for whatever reason just writing them to the directory structure with the zero padding would help. So the option might be:
EVENT_ID_PADDING=[yes|no]
At least with that you'd have (00001-99999, 00001, etc). Any trickiness to dealing with events in the file system would only happen when the ID's roll over back to 1 and that probably doesn't happen very often for most setups.