Fix save option settings...
Moderators: fgagnon, nikos, Site Mods
Fix save option settings...
Please allow option settings to be saved even when user has "save program state on exit" unchecked. Thanks.
I meant the options window. Most programs have an "apply" button. So xplorer2 should have one, too.narayan wrote:"Apply" button is provided in a dialog box, to mean "apply the current settings and continue using the dialog box". That is not applicable here, as there is no dialog box in the first place.
Well, the Options window is modal: Once it is launched, you can't use the main x2 window. Therefore the Apply button won't be useful there.
On the other hand, I don't see any advantage in making this window non-modal. Can you think of any operation where you need to keep the options windows available at hand, even as you have returned to x2 to resume your work?
Applying the current changes in settings are useful when you can't decide in advance what value to set for a parameter; and therefore you must set it interactively (through trial-and-error). In that case, you need simultaneous access to the settings window and the main application. That's where the Apply button is required.
In x2, all the choices are pretty straightforward, and you can set the values and exit the options dialog box before returning to work in the main x2 window.
***
Another way of looking at this issue: Saving the current settings is already provided through the menu (as mentioned); so there is little point in duplicating it in the Options window.
On the other hand, I don't see any advantage in making this window non-modal. Can you think of any operation where you need to keep the options windows available at hand, even as you have returned to x2 to resume your work?
Applying the current changes in settings are useful when you can't decide in advance what value to set for a parameter; and therefore you must set it interactively (through trial-and-error). In that case, you need simultaneous access to the settings window and the main application. That's where the Apply button is required.
In x2, all the choices are pretty straightforward, and you can set the values and exit the options dialog box before returning to work in the main x2 window.
***
Another way of looking at this issue: Saving the current settings is already provided through the menu (as mentioned); so there is little point in duplicating it in the Options window.
Yes, and we do appreciate your efforts.
A word about what happens in these forums: You will find that someone plays the devil's alternative to test the robustness of the idea. The ensuing dscussion lead to further refinement in the idea (or even some radically different ideas).
Certain ideas may be so straightforward that they get support without further discussion.
All this is good for the application.
*************
BTW what we post here (or in other threads) is NOT with finality. Only Nikos decides what is (or, is not-) to be done. So in this case, you are most welcome to counter the specific issues I (or others) raised.
Also keep in mind that some of the "unaccepted" ideas stay dormant for a long time till they find new value by combining with some other ideas. On the other hand, all "accepted" ideas will not get implemented in the very next version, because of time/resource constraints. So don't expect a Bugzilla-type response with clearly drawn implementation plans.
A word about what happens in these forums: You will find that someone plays the devil's alternative to test the robustness of the idea. The ensuing dscussion lead to further refinement in the idea (or even some radically different ideas).
Certain ideas may be so straightforward that they get support without further discussion.
All this is good for the application.
*************
BTW what we post here (or in other threads) is NOT with finality. Only Nikos decides what is (or, is not-) to be done. So in this case, you are most welcome to counter the specific issues I (or others) raised.
Also keep in mind that some of the "unaccepted" ideas stay dormant for a long time till they find new value by combining with some other ideas. On the other hand, all "accepted" ideas will not get implemented in the very next version, because of time/resource constraints. So don't expect a Bugzilla-type response with clearly drawn implementation plans.
I think you are looking for a quick way to not only change the settings of the current X² instance running in memory, but at the same time save those settings for all future instances.TsunamiZ wrote:[...]I meant the options window. Most programs have an "apply" button. So xplorer2 should have one, too.
That's is the difference between changing the settings (some of them, becuase the saved settings include much more than what is found in the dialog!) and making them permanent by saving them in the registry.
It is by design that these two are separated.
For instance: You might want to temporarily disable calculating folder sizes all the time (because you are on a slow network for instance), but in general you might want this option to be turned on. So you change the setting through the dialog, exit the dialog and that particular instance (and any other you spawn by starting new ones) will not calculate folder sizes anymore. But you don't want this setting to be permanent, because default it should calculate folder sizes.
That's the main reason chnging the settings for the curent running instance and making them permanent by saving them to registry (either automigically at exit or through menu 'Actions.Save setting now') are two separate actions.
Dumb questions are the ones that are never asked
How about a dialog box that opens upon closing xplorer² if the user has made changes and not saved them, asking if the user wants to save or discard these changes.
I have been caught by this split of functionality on several occasions and would welcome the program asking me if I want to keep or trash these changes. It seems to me this shouldn't be a hard thing to implement - a flag that says system state has changed which then runs a dialog upon program exit.
I have been caught by this split of functionality on several occasions and would welcome the program asking me if I want to keep or trash these changes. It seems to me this shouldn't be a hard thing to implement - a flag that says system state has changed which then runs a dialog upon program exit.
But you could do this for settings which are changeable by using the options dialog, no?? :twisted:nikos wrote:this isn't as easy as it sounds or rather it borders to inusability since each (most) thing you do in x2 has traces in history one way or another so you'd always be asked!
Last edited by JRz on 2005 Nov 08, 17:12, edited 1 time in total.
Dumb questions are the ones that are never asked