Total Commander

Excuse me if I do not write in the most appropriate topic, but I think the implementation is easy to design before the release of v8.51 ...

Personally consider useful many of the on/off commands, for example cm_SwitchHidSys that I will use as example to better understand me ...

As you know, this command toggles the display of certain file types, allowing the operation "on the fly" without having to enter the configuration menu for each small change.

This is a good thing and as long as the changes are few and far all is well: simply repeat the command to return to the original situation.

Considering that, apart from rare cases, are recorded in wincmd.ini (thus being permanent) when the changes are many and they change often becomes tedious to restore the original configuration step by step.

Wanting to solve the "problem" there would be two ways: making the temporary switch (automatic reset when the application exit) delegating to the configuration menu the static variation, or alongside "Save settings" on tab of the Configuration a Restore function, in other words to restore a backup made manually.

I hope it can be interesting ...

There are 10-11 of that kind of commands:
cm_SwitchHid
cm_SwitchSys
cm_SwitchHidSys
cm_SwitchLongNames
cm_Switch83Names
cm_SwitchOverlayIcons
cm_SwitchDirSort
cm_SwitchWatchDirs
cm_SwitchIgnoreList
cm_SwitchX64Redirection
(cm_SwitchSeparateTree) - 3 step switch

So what you are basically asking for is either:

1. Make additional new commands for only setting these options temporarily like:
cm_SwitchHidTemp
cm_SwitchSysTemp
cm_SwitchHidSysTemp
cm_SwitchLongNamesTemp
cm_Switch83NamesTemp
cm_SwitchOverlayIconsTemp
cm_SwitchDirSortTemp
cm_SwitchWatchDirsTemp
cm_SwitchIgnoreListTemp
cm_SwitchX64RedirectionTemp
(cm_SwitchSeparateTreeTemp)
or
2. Simply letting the current commands only work temporarily.
or
3. Making a new wincmd.ini parameter like SwitchCommandTemp=1, that determines whether or not the existing commands sets the options temporarily or permanetly.

Personally I would prefer the last approach (3).

Yes! Basically, the result is the same ... just "say" to the application from that moment on you will not have to write any changes in wincmd.ini unless it decides otherwise, and only through with a switch linked to the function key "SwitchCommandTemp", otherwise passing from the menu configurtazione move the hassle just somewhere else ...

The roads are different, but the result is the same, just choose the "least cost" in terms of programming and "upheaval" source: probably your solution (3) corresponds to this, it is sufficient to check-in routine of update function of wincmd.ini file the flag to inhibit any update total or partial (but in this case the changes on sources would be "heavy").

From what little I know about programming, I know that a change in these terms is not "expensive" ... we hope that Ghisler (Author) consider this interesting and engages in to producing it.

retalv,
You can try Autorun plugin, it allows launching some commands at TC exit, including writing to INI, so you can launch commands to restore desired values to your 'defaults'.

BTW it isn't good that you:
1. Gave absolutely meaningless title to your topic,
2. Made a suggestion using forum for bug reports.

2. Made a suggestion using forum for bug reports.

To moderators: please move this thread to "TC suggestions (English)"

petermad,
This forum section unfortunately does not have moderators.

Roman

[mod]Moved to suggestions[/mod]