Page 2 of 2
Re: Request: Actions > File Operations
Posted: Thu Jun 09, 2016 7:54 pm
by cday
XnTriq wrote:How about a “Reset” action?
Revert to the initial state of the input files and specify a new output directory.
All subsequent actions will be applied to the originals and the results will be saved in a different destination folder.
Interesting insight, but is there actually a need for the "Reset" action?
If the input files are not modified (not deleted or otherwise altered by any setting on the Output tab) then the settings on the Actions and Output tabs can simply be edited as required and Convert pressed again?
In general, will there be any reason to modify the input files?
As the edits required to the Actions and Output settings will probably usually be minor, running three times (for example) with the same input files and only minor changes to the settings should provide a usable workaround pending any eventual integrated solution?
Re: Request: Actions > File Operations
Posted: Thu Jun 09, 2016 9:15 pm
by XnTriq
cday wrote:[…] but is there actually a need for the "Reset" action?
Yes, I think so.
HeyYCw is one of many users who're looking for a way “to perform a sequence of actions on a master image and export different versions to multiple destinations”
in one go.
- XnView Classic
XnView MP
XnConvert
Let me give you an example. The following seems to be a typical use case:
Re: Request: Actions > File Operations
Posted: Thu Jun 09, 2016 11:54 pm
by HeyYCw
One last thought before I let this go:
In the settings, if there was a "power user" option that displayed an alternate UI (eg the 3-in-1 tab), you could maintain the simple, elegant current UI for existing user-base; but at the same time, expand XnConvert's reach to power-users who have more complex image processing requirements.
Ultimately the underlying functionality between the two views is the same; it's all in how that functionality is channelled through the UI.
Re: Request: Actions > File Operations
Posted: Wed Jun 15, 2016 3:30 pm
by XnTriq
@Pierre: Do you think implementing this…
XnTriq wrote:How about a “Reset” action?
Revert to the initial state of the input files and specify a new output directory.
All subsequent actions will be applied to the originals and the results will be saved in a different destination folder.
… would have a negative effect on user-friendliness?