Posts: 15
Threads: 7
Joined: Nov 2019
Posts: 15
Threads: 7
Joined: Nov 2019
Especially with a mac touchpad, it's easy to accidentally touch on a different part of the file tree interface, and end up switching away from the sequence you're working on at that moment.
Sometimes you get the:
Unsaved changes!
You have unsaved XMP-Metadata
Do you want to save?
(No/Yes)
But other times it just switches immediately.
In both cases there is no way to mark this action as an error.
The unsaved changes dialog should have a cancel/go back button, that simply dismisses the dialog and leaves things as they were before the errant click. This ideally would avoid reloading the sequence, or anything else that takes a long time.
It's also possible that there are other situations the user could end up in where the sequence is being actively processed, but XMP metatada isn't yet modified. It would be nice to have a sequence change validation dialog in these cases as well.
Sometimes you get the:
Unsaved changes!
You have unsaved XMP-Metadata
Do you want to save?
(No/Yes)
But other times it just switches immediately.
In both cases there is no way to mark this action as an error.
The unsaved changes dialog should have a cancel/go back button, that simply dismisses the dialog and leaves things as they were before the errant click. This ideally would avoid reloading the sequence, or anything else that takes a long time.
It's also possible that there are other situations the user could end up in where the sequence is being actively processed, but XMP metatada isn't yet modified. It would be nice to have a sequence change validation dialog in these cases as well.