Thanks for tracking these.
Here's some followup:
- Older versions allowed us to "edit" the settings of a saved session and login without saving it again, very useful to test changes before saving the options.
I'm aware of this regression. Will see how people miss this.
One advantage of the old behavior is that it does not change (or even touch) the config file, avoiding any write error; another advantage is security, as if you do an accidental or undesirable change to an option and forget to change it back. We could also use the settings of one arbitrary site and change only the ip or connection type, for example, to log in once using different settings.
The new way looks much less practical, may it be to reuse settings temporarily, test new settings, editing advanced options or other. Imo, it is now a noobfied dialog, from the perspective of usability.
What advantage inspired you for changing its design?
- Missing options in Tools menu under Site Manager (aka New Session) when it is opened from toolbar.
That was always like this. It's by purpose as some of these options chance configuration globally, what would cause troubles then done while the application is running. What particular option would you find useful while application is running?
Not really needing this, but I just perceived the problem when was trying to find the Clean Up item (which don't have what I needed). By the way, something I was needing was an easy way to clear cached things that make the config file a growing monster (mostly the CDCache parts of the .ini, I think).
Btw, the About and Check Updates are two things that must not cause any harm to be there.
Other than that, I think much more trouble happens when two or more instances of WSCP are running, each one may change settings based on a different edition of the config file when it was loaded in memory, and then each one that is closed will replace the file with the settings it has in memory. Very often it causes the lost of settings, bookmarks, etc. made in one instance but not in the others.
I also don't like how WSCP locks all the background screens when some kind of dialogs are opened (e.g. the 'Connecting to...', Login, Preferences etc.). In many programs they live together with the rest and don't need to block access to other parts of the program. This is specially good, for example, when we are working with folders/files and want to open a new connection, but want to continue working on the current tab while it connects in another tab. (Maybe this can be thought as the function "open link in a background tab" of browsers).
- In the new Overwrite Confirmation dialog, I would like to be able to move from Yes to No (and vice-versa) using the right/left keys instead of only tab.
This request has been added to the tracker:
This was always possible with the normal buttons which don't have a drop-down menu.
Same thing happens in the Login dialog with the new buttons.
Another thing I noted these days is this: toggling between tabs does not memorize the position of scrollbar and always go back to start, I mean, it goes back to where the last selected line is (after changing tabs, the scroll position makes that line the last in the list). I personally think it is more intuitive to remember the scrollbar position I set, not the line I eventually selected (especially when no line was selected by the user, ".." line is always selected).