Suggestion: Add leading zeroes to extension numbering

When you have more than one file created for an image set, Image for Windows (and I assume DOS & Linux) creates files with extensions of .1, .2, .3, etc. For me this was rarely a problem, either because (back in the day) if I created multiple files, each the size of an optical disk (be they CD, DVD or BD), I would label/number the disks manually, so how the file numbering looked wasn't that important. Later on, when backing up to another large storage device, I normally created image sets of maximum size, so the number didn't exist. Or if I did limit the file size, there were still relatively few numbers.
However, now that I am starting to store my backups in the cloud, many services have limits to the size of each file, so I'm back to creating multiple files, and having the numbering as-is means the sorting by extension causes things to be displayed in non sequential order (.1, .10, 11, 12... .19, .2, .20, 21... .29. .3, .30. 31, etc.).
If the user had the option to pad the extension numbers with leading zeroes (.001, .002, .003... .010, .011, - you get the idea!) then the proper sorting would work again.
I'd suggest that the user be given both the option to include leading zeroes, as well as specify the minimum number of digits the extension should have. By having this as a MINIMUM number, the system will still work if a 2 digit minimum setting exceeds 99 files - the sorting will still be off for that set, but the backup will continue with .100, .101, etc. (and the next time the user may change to a 3 digit minimum).
Not something that needs to be immediately implemented, but I think it would be a useful feature.
Anyone else like this suggested option?
However, now that I am starting to store my backups in the cloud, many services have limits to the size of each file, so I'm back to creating multiple files, and having the numbering as-is means the sorting by extension causes things to be displayed in non sequential order (.1, .10, 11, 12... .19, .2, .20, 21... .29. .3, .30. 31, etc.).
If the user had the option to pad the extension numbers with leading zeroes (.001, .002, .003... .010, .011, - you get the idea!) then the proper sorting would work again.
I'd suggest that the user be given both the option to include leading zeroes, as well as specify the minimum number of digits the extension should have. By having this as a MINIMUM number, the system will still work if a 2 digit minimum setting exceeds 99 files - the sorting will still be off for that set, but the backup will continue with .100, .101, etc. (and the next time the user may change to a 3 digit minimum).
Not something that needs to be immediately implemented, but I think it would be a useful feature.
Anyone else like this suggested option?