B3: Script in batch convert can't be disabled
Moderators: helmut, XnTriq, xnview
B3: Script in batch convert can't be disabled
If I choose any script in batch convert - general tab, I can't disable it. I have to switch to transf. tab, click 'remove all', but script below is still not updated (but not used).
There should be possibility to disable script on both tabs/pages with:
- [ [x] [script name... ]
or:
- empty item (or "None") in drop-down menu
XnView 1.82 <x>
There should be possibility to disable script on both tabs/pages with:
- [ [x] [script name... ]
or:
- empty item (or "None") in drop-down menu
XnView 1.82 <x>
Last edited by Dreamer on Sat Feb 18, 2006 4:17 pm, edited 1 time in total.
Re: B3: Script in batch convert can't be disabled
The first solution (with checkbox) could be used for quickly enabling/disabling the script last used.Dreamer wrote:If I choose any script in batch convert - general tab, I can't disable it. I have to switch to transf. tab, click 'remove all', but script below is still not updated (but not used).
There should be possibility to disable script on both tabs/pages with:
- [ [x] [script name... ]
or:
- empty item (or "None") in drop-down menu
Re: B3: Script in batch convert can't be disabled
Yes, already suggested by me, here is reply from Pierre: "i'm not sure that checkbox will be good... ".helmut wrote:The first solution (with checkbox) could be used for quickly enabling/disabling the script last used.
But I think drop-down menu should not be greyed out, it sould be possibe to choose the script also if it's disabled, then it should be enabed automatically.
Re: B3: Script in batch convert can't be disabled
We do need something to disable a chosen script. A checkbox is better than an entry "Empty", I think.Dreamer wrote:Yes, already suggested by me, here is reply from Pierre: "i'm not sure that checkbox will be good... ".helmut wrote:The first solution (with checkbox) could be used for quickly enabling/disabling the script last used.
Not sure about this one. In "File search" dialog, checkboxes disbable the appropriate functionality, which is good since user can easily see which search options are active and which ones are not.Dreamer wrote:But I think drop-down menu should not be greyed out, it sould be possibe to choose the script also if it's disabled, then it should be enabed automatically.
If possible, things should be consistent throughout the application.
Re: B3: Script in batch convert can't be disabled
OK, but it's not the same, if checkbox would be unmarked, area next to it would be empty (instead of greyed out), same as now if you open dialog, so it would be clear that it's disabled. I think it's more important to quickly enable script.helmut wrote:Not sure about this one. In "File search" dialog, checkboxes disbable the appropriate functionality, which is good since user can easily see which search options are active and which ones are not.Dreamer wrote:But I think drop-down menu should not be greyed out, it sould be possibe to choose the script also if it's disabled, then it should be enabed automatically.
If possible, things should be consistent throughout the application.
But when I select script, I suppose it will be used.xnview wrote:Not sure that checkbox must be checked automatically???Dreamer wrote:Checkbox added in RC1, but:
When script is chosen, checkbox in not marked automatically.
If not, it should be greyed out, but I don't like this solution, there would be 2 steps instead of one to choose script.
Checkbox should help, not make it more complicated.
Small suggestion - last used script could be selected when dialog is opened, then I have to just enable checkbox to apply it.
Fixed in RC2, but checkbox can't be unmarked then.
Also, if checkbox is marked, last used script should be selected/enabled automatically (only if there is no action in second tab).
And - if some action on second tab is moved to right side (it's enabled), checkbox should be enabled automatically too (but actual operations should be used, not last used script) - because if user choose some action(s) he expects that this action(s) will be used when he press "Go" IMO.
Also, if checkbox is marked, last used script should be selected/enabled automatically (only if there is no action in second tab).
And - if some action on second tab is moved to right side (it's enabled), checkbox should be enabled automatically too (but actual operations should be used, not last used script) - because if user choose some action(s) he expects that this action(s) will be used when he press "Go" IMO.
Fixed, but when I unmark checkbox, script is still used - new bug. I must remove all actions manually.Dreamer wrote:Fixed in RC2, but checkbox can't be unmarked then.
Not changed, but not too important...Dreamer wrote:Also, if checkbox is marked, last used script should be selected/enabled automatically (only if there is no action in second tab).
My idea about checkbox was a bit different, now it's used as "enable/disable script", my idea was to "enable/disable transformations", it would be more useful then. Now it's useless IMO. Item "No action" would be better maybe, or checkbox could be used to "enable/disable transformations", but I'm not sure if it's not too late.
Yes too lateDreamer wrote: Not changed, but not too important...
My idea about checkbox was a bit different, now it's used as "enable/disable script", my idea was to "enable/disable transformations", it would be more useful then. Now it's useless IMO. Item "No action" would be better maybe, or checkbox could be used to "enable/disable transformations", but I'm not sure if it's not too late.

Pierre.