-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve filename template for the date and time format #188
Labels
Milestone
Comments
+1 |
yep,as the guy said,it's hard to select file which contains space in shell or terminal,hope more format |
Currently the placeholders are replaced by gnome shell (https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/main/js/dbusServices/screencast/screencastService.js#L296 - method |
adangel
added a commit
to adangel/EasyScreenCast
that referenced
this issue
Nov 29, 2021
…st#188) This replaces the default gnome shell functionality allowing more flexibility: E.g. now all the placeholder of GLib.DateTime.format are possible - with the exception of `%d` and `%t`, which keep their old behaviour. Additionally, whitespaces are replaced by underscore. This make it possible to use now the template `Screencast_%Y%m%0e_%H%M%S` in order to get a filename like `Screencast_20171230_091325.webm`. (Note: `%0e` needs to be used instead of `%d` for compatibility).
adangel
added a commit
that referenced
this issue
Feb 4, 2022
Add a custom _generateFileName function in utilrecorder (#188)
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
feature request
I was not able to find in documentation if it is possible
now I have the saved file in format
Screencast_%d_%t
which generate something like
Screencast_12-30-2017_09:13:25 AM.webm
but I'll prefer to generate something like this
Screencast_20171230_091325.webm
( the general format )
Screencast_YYYYMMDD_HHmmss.webm
which is easier to save on a web server and create link to it automatically (no spaces and special characters involved)
The text was updated successfully, but these errors were encountered: