Extended Menus for TC 11.03 - Updated February 21st 2024

[Horst.Epp]

2petermad
Thanks, I made a branch view of the whole archive and overlooked the wcmd_win10amd64_eng.zip
I even have an Everything index for archives, but this currently doesn't support nested archives

[petermad]

Updated version 11.03 is now available for download (links in first post):

New:

• Updated the Help files (Totalcmd.hlp and *Dark.chm) in the addons package.
• Added Menu item to run a separate instance of Total Commander as different user.

_________________

Nyt:

• Opdateret Hjælpefilene (Totalcmd.hlp og *Dark.chm) i udvidelsespakken.
• Tilføjet Menupunkt til at køre Total Commander som anden bruger.

_________________


See first post on how to use the menus when 32bit and 64bit TC are sharing the same installation folder and the same wincmd.ini

[Helix751]

The 'Windows 10' menu has access to 2 button bars; "Control Panel" and a 'Windows 10' specific bar.

When opening the Control Panel bar, returning with the arrow goes back to the Windows 10 bar, but the arrow in this bar shows error because it points to a 'default.bar' location inside the Roaming\GHISLER dir.

%COMMANDER_INI%\..\default.bar

I have a very old legacy installation, and have always had the button bar files inside the totalcmd program directory (%COMMANDER_PATH%), not in the profle dir. Which is the better place to put button bars?

Note: TC v11.03 introduces a new variable anyway: %COMMANDER_INI_PATH%, which would be more appropriate than using the %COMMANDER_INI%\..\default.bar parameter

[petermad]

I have a very old legacy installation, and have always had the button bar files inside the totalcmd program directory (%COMMANDER_PATH%), not in the profle dir. Which is the better place to put button bars?

I have my default bar in TC's program folder too, but I use the path to the profile dir (where wincmd.ini is located), because that is what TC uses if the program dir is write protected, if it for exampkle is insctalled in "C:\Program Files\totalcmd". If you have for example your TC installed in C:\Totalcmd, and you have UseIniInProgramDir=7 in your wincmd.ini file, then my Menus will use C;\totalcmd as the dir for the default.bar.

Where do you have your wincmd located?

Note: TC v11.03 introduces a new variable anyway: %COMMANDER_INI_PATH%, which would be more appropriate than using the %COMMANDER_INI%\..\default.bar parameter

I know - but I decided to keep using %COMMANDER_INI%\..\ for backwards compatability. %COMMANDER_INI_PATH% is mainly introduced because there apparantly where some 3rd party programs that couid not handle %COMMANDER_INI%\..\ - but in my menus there are no such problems.

[Helix751]

Thanks for your reply.

Where do you have your wincmd located?

COMMANDER_INI=%APPDATA%\GHISLER\wincmd.ini
COMMANDER_INI_PATH=%APPDATA%\GHISLER
COMMANDER_PATH=C:\totalcmd

[petermad]

2Helix751
Yes, when you have TC installed in a folder that is not write restricted like c:\totalcmd (where I also have my TC installed), but you have chosen to have your configuration files in %APPDATA%\GHISLER - then TC will not relocate the default.bar to %APPDATA%\GHISLER

My menu supports these two situations:
1. TC is installed in a write-protected dir like %ProgramFiles% - the default.bar is assumed located in %COMMANDER_INI\..\% = %COMMANDER_INI_PATH%
2. TC is installed in a dir with write privileges like c:\totalcmd - UseIniInProgramDir=1-7 in wincmd.ini is assumed and this also locates default.bar in %COMMANDER_INI\..\% = %COMMANDER_INI_PATH% which in this case is c:\totalcmd.

If I instead of using %COMMANDER_INI%\..\default.bar for the return button just used: default.bar - it would work in your setup - but it would not work in the two setups here above.

A huge amount of users probably uses the setup described at 1.
I think most people that install in a folder with write privileges as described in 2., does it to keep all of TC in one folder (plus sub-folders of course), hence are using the UseIniInProgramDir=7 to keep the configuration files and files like default.bar in TC's program folder.

The user can also have chosen to use a completely different bar-file in a completely different folder as default ( I use c:\totalcmd\Language\wcmd_pm_dan\pm_dan.bar) - and there is no way I can detect that either.

So I think using %COMMANDER_INI%\..\default.bar covers most users

There actually is a way of opening the users default bar without knowing the location and that is by using:

Code: Select all

cmd1=cm_VisButtonbar 2,cm_VisButtonbar 1

It doesn't change back to the default bar as smoothly, but maybe I should use that solution.

It will not hide the back arrow, when the bar is opened as a menu, but this is not a problem with those button bars in my menus that needs to point back to the default bar.

If you want to do it yourself for now, it is the cmd1= line that has to be changed in the files win*_1_???.bar, win*_3_???.bar and win*_4_???.bar files in the %COMMANDER_PATH%\Language\wcmd_win*_??? folder.

[Helix751]

If you want to do it yourself for now, it is the cmd1= line that has to be changed in the files win*_1_???.bar, win*_3_???.bar and win*_4_???.bar files in the %COMMANDER_PATH%\Language\wcmd_win*_??? folder.

Yes, That's what I did. Thanks for the complete answer and for your Extendended Menus in the 1st place.

[oko]

typo in preferences-languages:
The Czech language: Ceština should be Čeština or Český.
The Ukranian should be Ukrainian.

[petermad]

2oko
I tried to change the capital C to capital C with hacek. But since the Languages.bar file is in ANSI it does not really work. Here - with my locale - it turns up as Èeština - I dont feel inclined change the mnu file to UTF-8 just for that.

Is Ceština a big eye sore? - if it is I will just thage th items from "Ceština (Czech)" to "Czech"

I fixed the Ukrainian (which btw. was correct in the Languages.bar file) - thanks

See also https://ghisler.ch/board/viewtopic.php?p=452294#p452294

[oko]

2petermad
Yes, Ceština is a big eye sore for me See my answer in viewtopic.php?p=452301#p452301

[oko]

As I found out, there are:
- default.bar (factory)
- default.bar (used)
- default bar (any bar defined by user as default)
Default.bar does not have to be default bar. In many cases it is. But if other bar is configured as default, default.bar can not be default bar too (in this case it is only named default but not default one indeed).
In this meaning the Preferences-Button Bars-Default Button Bar items can be precised:
- Load Button Bar from "default.bar"
- Load Button Bar 2 from "vertical.bar"
- Load Default Button Bar (as configured)
- Load Default Button Bar 2 (as configured)

[petermad]

2oko

I have made a solution that will return to the used default bar when going back from the language bar - it will be in the next release.

In the meantime replace cmd1 in the Languages bar with: cmd1=cm_VisButtonbar 2,cm_VisButtonbar 1

[oko]

I only suggested to be renamed (precised in text not in function) four items in Extended menu in Preferences-Button Bars to better descript what they do. But yes, the meaning of "default" has consequences that any command to return to default bar should return default bar, not "default.bar", so you made good solution. In first moment I had not understood what has my suggestion to Extended menu common with Language bar

[oko]

There could be distinguished:
- Open file
- View file (e.g. by Lister F3)
- Open (or load) something from file (e.g. lng/mnu/bar files)

E.g. in case of .lng/.mnu files the file can be opened/viewed (to edit or view the file) OR language/menu can be loaded from that file. If e.g. a command loads (opens) the bar, the command should not be named "Open bar file", but it should be named "Open bar from file" or "Load bar from file". A command named "Open bar file" expects to open bar file to view or edit the file itself.
In this meaning there could be proper menu items renamed to precise what they do. I noticed this items:
actual:

POPUP "Language/Menu"
...
MENUITEM SEPARATOR
MENUITEM "Open Langua&ge/Menu File under Cursor", em_ext_openlanguagefile
MENUITEM "Open Men&u File under Cursor", em_ext_openmenufile
MENUITEM "Open Language/Menu Button Bar", em_ext_langbar
...

suggested:

POPUP "Language/Menu"
...
MENUITEM SEPARATOR
MENUITEM "Load Langua&ge/Menu from File under Cursor", em_ext_openlanguagefile
MENUITEM "Load Men&u from File under Cursor", em_ext_openmenufile
MENUITEM "Load Language/Menu Button Bar", em_ext_langbar
...

In 3rd item I am not sure but I think it should be renamed to "Load Language Button Bar", since menu is not changed.

[oko]

In filter - show spredsheets - you must add many years actual standard formats: .xlsx, xlsm, xlsb, xltm, xlam (see https://en.wikipedia.org/wiki/Microsoft_Excel). Also pptx, ppsx formats to presentations. To more categories you can add opendocument formats: see https://en.wikipedia.org/wiki/OpenDocument