-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
startdate/enddate aren't picking up (optional) time part of the argument #8
Comments
The problem is the argument parsing code only is looking at the first argument after the "-startdate" (which is the date) and because of the space between the date/time, it's not picking up the time part when parsing the datetime string. As a work-around I tried using
(to remove the space between date and time), and it worked fine and as expected. |
Very well noticed @dbkinder1! Thanks for sharing your workaround as well. Another option would be to wrap the date/time in (double or single) quotes, i.e.:
I'll update the samples in the tool to reflect this. |
Resolved in version 2.0.1.1. Thanks for your contribution! |
Thanks @KoenZomers and for completeness you might update the images in https://github.com/KoenZomers/RingRecordingDownload/blob/master/README.md that are missing quoted date/time arguments. :) BTW, by using your nice ring downloader, together with |
Done! Cool idea about the timelapse! |
Assuming I've got the format right (as presented in the online examples), the tool is parsing the date, but not the time from the command line. (Notice the output from the command isn't picking up the time part of the
-enddate
argument.)The text was updated successfully, but these errors were encountered: