by helmut (Posted Tue Sep 06, 2016 9:26 pm)
The configuration wizard is a first-start wizard. It is displayed only when starting XnView for the very first time (e.g. after installation). What you set here is the location of the .ini file and the system integration (e.g. entries in context menu or icon on desktop). XnView needs a location for saving its configuration, so in fact you cannot start without making any decision at all and deciding later.
Current behaviour
I've just tried out the behaviour of "OK" and "Cancel". If you confirm the configuration without changing anything beforehand by pressing "OK" you get the 100% same .ini file as by pressing "Cancel".
What should "Cancel" do?
We all think is that the current behaviour of "Cancel" is somehow wrong, but what would be the correct behaviour? Actually, it's the "Cancel" button itself which is wrong: At this point you have to make a decision because XnView will at least need to know the location for storing its settings. You cannot proceed without making a decision, i.e you cannot cancel. Alternatively, the "Cancel" button might cancel the program, but why should you quit the program that you've just started? That would be user-unfriendly and really unexpected behaviour. So the "Cancel" button just doesn't make sense, here.
Conclusion/Suggestions
- Remove the "Cancel" button and move the "OK" button to the center of the dialog.
- As Mixer suggested, a "Default values" button could be added (replacing the "Cancel" button). But I'd vote against such a "Default values" button for various reasons:
- The button's label is very long and even longer in some translations.
- It's only very few settings that the user might have changed and would be reset.
- The button will raise more questions than answers which is contrary to a quick-start.
- The button ruins the screen layout
Just my 2 cents...
Read Main Topic
The configuration wizard is a first-start wizard. It is displayed only when starting XnView for the very first time (e.g. after installation). What you set here is the location of the .ini file and the system integration (e.g. entries in context menu or icon on desktop). XnView needs a location for saving its configuration, so in fact you cannot start without making any decision at all and deciding later.
Current behaviour
I've just tried out the behaviour of "OK" and "Cancel". If you confirm the configuration without changing anything beforehand by pressing "OK" you get the 100% same .ini file as by pressing "Cancel".
What should "Cancel" do?
We all think is that the current behaviour of "Cancel" is somehow wrong, but what would be the correct behaviour? Actually, it's the "Cancel" button itself which is wrong: At this point you have to make a decision because XnView will at least need to know the location for storing its settings. You cannot proceed without making a decision, i.e you cannot cancel. Alternatively, the "Cancel" button might cancel the program, but why should you quit the program that you've just started? That would be user-unfriendly and really unexpected behaviour. So the "Cancel" button just doesn't make sense, here.
Conclusion/Suggestions
- Remove the "Cancel" button and move the "OK" button to the center of the dialog.
- As Mixer suggested, a "Default values" button could be added (replacing the "Cancel" button). But I'd vote against such a "Default values" button for various reasons:
- The button's label is very long and even longer in some translations.
- It's only very few settings that the user might have changed and would be reset.
- The button will raise more questions than answers which is contrary to a quick-start.
- The button ruins the screen layout
Just my 2 cents...
Read Main Topic