tcm75rc1: internal associations bug ?

[Boofo]

Hacker,

I didn't know you could pick which association to launch it with in the file lists at will. How would you do that?

I see what you are saying now. That would be a problem unless it was added for the other areas, too, somehow.

[Lefteous]

But how would you solve it in the interface?

By extending the buttons right click menu. The first section of this menu could contain the primary and alternative executables for the filetype. If the user defined it this would include the Windows association as well.

[Boofo]

2Lefteous

That answers my question on the file lists, too. Thanks!

[Hacker]

Lefteous,

By extending the buttons right click menu.

Then there are aliases, hotkeys and the (start) menu.

Roman

[petermad]

I didn't know you could pick which association to launch it with in the file lists at will. How would you do that?

Either like this (gives you 5 options with cm_ContextMenu (right-click)
or 7 with cm_ContextMenuInternalCursor)

Code: Select all

Filter5=*.jpg *.gif *.png *.bmp
Filter5_open=**
Filter5_Imagine=""%COMMANDER_PATH%\PLUGINS\WLX\imagine\Imagine.exe" "%1""
Filter5_PaintShop Pro="%PROGRAMFILES%\PSP\PSP.EXE" %1
Filter5_IrfanView="%PROGRAMFILES%\IrfanView\i_view32.exe" "%1
Filter5_XnView=""%PROGRAMFILES%\XnView\xnview.exe" "%1""
Filter5_Lister=""%COMMANDER_PATH%\TOTALCMD.EXE" /S=L "%1""
Filter5_Default=**

Or like this (gives you 3 options with cm_ContextMenu (right-click) or 4 options with cm_Return (Enter or double-click)):

Code: Select all

Filter1=*.txt *.ini *.css *.js
Filter1_open=*
Filter1_Metapad=""%COMMANDER_PATH%\TOOLS\metapad.exe" "%1""
Filter1_PlainEdit=""%PROGRAMFILES%\PlainEdit\PlainEdit.exe" "%2""
Filter1_Notepad=""%SYSTEMROOT%\notepad.exe" "%1""
Filter1_Default=**

[Lefteous]

Then there are aliases, hotkeys and the (start) menu.

Basically there are commands for to open with the default association and commands to display a menu with all the others. They can be used everywhere.
The suggested buttonbar's right click extension menu was just an optimization and might not be absolutely necessary.

[Boofo]

2petermad,

Thank you for the help, sir. I did not know about that. It works pretty slick.

[Hacker]

Lefteous,

Basically there are commands for to open with the default association and commands to display a menu with all the others.

I think you are talking about something different than Boofo was. If I understood Boofo correctly, he suggested that if he clicks on image.jpg and the IA is set to open it in XnView, then defining a button pointing to image.jpg should also open it in XnView instead of the default SA. There currently is no internal solution neither for that nor any commands to display a menu with any other associations. Only for a file in the filelist. At least I am not aware of any.

Roman

[Balderstrom]

ButtonBar Icon

Command: cm_Return
Parameters: %S

Internal Association:

Filter2=*.wav
Filter2_open=""C:\Program Files\¤IMAGE\IrfanView\i_view32.exe" "%1""

Click Button, IrfanView plays wav.

Thus having a single button with an action cm_Return, will allow you to open any file which you have assigned an Internal Association. Same with having a "cm_Return" in one of your MainMenu drop downs.

BTW, if you do an internal association for various sound files, you'll find the windows icons for those here in system32\mmsys.cpl

[Hacker]

Balderstrom,

Thus having a single button with an action cm_Return, will allow you to open any file which you have assigned an Internal Association

But only a file in the file panel.

Roman

[Balderstrom]

I'm not sure what you mean Hacker,
cm_Return will work for ButtonBar, DirectoryHotlist, MainMenu

As well we have cm_ContextMenu, cm_ContextMenuInternal and cm_ContextMenuInternalCursor, which can be assigned to a HotKey...

And with cm_Return, if you don't have an InternalAssociation defined, then control is passed over to Windows to figure out how to launch the item.

The only thing it doesn't work for is archives, unless you change your config and
uncheck [x] Treat archives like directories.

[Lefteous]

I think you are talking about something different than Boofo was.

No I guess I do.

[Boofo]

Lefteous,

Basically there are commands for to open with the default association and commands to display a menu with all the others.

I think you are talking about something different than Boofo was. If I understood Boofo correctly, he suggested that if he clicks on image.jpg and the IA is set to open it in XnView, then defining a button pointing to image.jpg should also open it in XnView instead of the default SA. There currently is no internal solution neither for that nor any commands to display a menu with any other associations. Only for a file in the filelist. At least I am not aware of any.

Roman

Yes, sir, that is what I meant.

[Boofo]

I'm not sure what you mean Hacker,
cm_Return will work for ButtonBar, DirectoryHotlist, MainMenu

As well we have cm_ContextMenu, cm_ContextMenuInternal and cm_ContextMenuInternalCursor, which can be assigned to a HotKey...

And with cm_Return, if you don't have an InternalAssociation defined, then control is passed over to Windows to figure out how to launch the item.

The only thing it doesn't work for is archives, unless you change your config and
uncheck [x] Treat archives like directories.

Internal Associations ONLY work for the file panels, not the buttonbar, hotlist, etc.

[Balderstrom]

Boofo, that is just not true.

Make an internal association, and put cm_return on a button like I indicated. It WILL open your Internally associated program.

Otherwise, I don't know what you are referring to.
In what instance would you ever launch a file.ext that isn't in the FileList?