You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many apps (such as Microsoft Office, etc.) have an "Open Recent" or similar
menu item under the File menu. In LosslessCut, this could list recent source
videos (and optionally project files, exported videos, etc.). @mifi are you open to this functionality, either as a user-submitted PR or
implemented yourself (as I don't know your preferences)?
If you're open to part 1, optional extra semi-related functionality:
LosslessCut could automatically restore cut times for recent files. I'd
love to see it remembered for many recent files (20? 100?), but even if only
remembered for the most recent file that would be better than nothing for me.
LosslessCut would store the times in its existing common settings file or
similar. This functionality has overlap with project files but would be
automatic without creating extra user filesystem files.
If LosslessCut remembered recent files and/or exports, loading an
exported video could prompt the user if they want to instead load the
original source video using the previous cut times. LosslessCut could
remember recent cut times in its settings file, or autoload cut times if the
user used the standard export filename format.
For part 2, LosslessCut could match videos based on full path, or if no full
path matches, filename match.
Are you open to any/all of these ideas?
The text was updated successfully, but these errors were encountered:
Many apps (such as Microsoft Office, etc.) have an "Open Recent" or similar
menu item under the File menu. In LosslessCut, this could list recent source
videos (and optionally project files, exported videos, etc.). @mifi are you open to this functionality, either as a user-submitted PR or
implemented yourself (as I don't know your preferences)?
This sounds like a good feature to have. However I think before implementing too many new features that cross the main-renderer-process-boundary in electron I think I want to #1377 - or else that job is going to grow bigger in the future. E.g. I don't want to add any more features depending on @electron/remote or nodeIntegration right now.
LosslessCut could automatically restore cut times for recent files. I'd
love to see it remembered for many recent files (20? 100?), but even if only
remembered for the most recent file that would be better than nothing for me.
LosslessCut would store the times in its existing common settings file or
similar. This functionality has overlap with project files but would be
automatic without creating extra user filesystem files.
So you mean have an option to disable project files (already exists), and another option to save/load cutpoints per file in one central location (e.g. user's app data folder)?
2. If LosslessCut remembered recent files and/or exports, loading an
exported video could prompt the user if they want to instead load the
original source video using the previous cut times. LosslessCut could
remember recent cut times in its settings file, or autoload cut times if the
user used the standard export filename format.
Not sure what is the use case for this. I've never heard it requested before but can leave it open to see if more interest. Is it related to #1385 ?
I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first
Description
Many apps (such as Microsoft Office, etc.) have an "Open Recent" or similar
menu item under the File menu. In LosslessCut, this could list recent source
videos (and optionally project files, exported videos, etc.).
@mifi are you open to this functionality, either as a user-submitted PR or
implemented yourself (as I don't know your preferences)?
If you're open to part 1, optional extra semi-related functionality:
LosslessCut could automatically restore cut times for recent files. I'd
love to see it remembered for many recent files (20? 100?), but even if only
remembered for the most recent file that would be better than nothing for me.
LosslessCut would store the times in its existing common settings file or
similar. This functionality has overlap with project files but would be
automatic without creating extra user filesystem files.
If LosslessCut remembered recent files and/or exports, loading an
exported video could prompt the user if they want to instead load the
original source video using the previous cut times. LosslessCut could
remember recent cut times in its settings file, or autoload cut times if the
user used the standard export filename format.
For part 2, LosslessCut could match videos based on full path, or if no full
path matches, filename match.
Are you open to any/all of these ideas?
The text was updated successfully, but these errors were encountered: