Is it necessary to define same file associations whether in windows and in Total Commander?
I like to run TC on my portable disk. I want to associate some kind of files to the programs on my portable disk without changing window's file associations. This is usefull to work on a guest PC.
Is it possible to define different file association in TC
Moderators: Hacker, petermad, Stefan2, white
Not at the moment, but suggestions exist.Is it necessary to define same file associations whether in windows and in Total Commander?
Use C.A.F.E.I want to associate some kind of files to the programs on my portable disk without changing window's file associations.
HTH
Roman
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.
Thanks to friends.
Before my post, I have searched "association" in forum not in wiki. Because, I did not know to find something there. But now, I have learned it lately.
C.A.F.E is very interesting! It changes windows associations temporarily while it runs. It is also good news that stable (not beta) PortableApps will be available soon for it.
But, I prefer "Internal association system in Total Commander". Is there any light to use it soon?
best regards
Before my post, I have searched "association" in forum not in wiki. Because, I did not know to find something there. But now, I have learned it lately.
C.A.F.E is very interesting! It changes windows associations temporarily while it runs. It is also good news that stable (not beta) PortableApps will be available soon for it.
But, I prefer "Internal association system in Total Commander". Is there any light to use it soon?
best regards
Well, If you don't have the need to open files with enter(or double click).
Configuration→Edit/View→Associations...
then use Alt+F3(or F3) to open files.
Also you can use F4Menu or ChoiceEditor as "Editor for F4" and open files with F4
Configuration→Edit/View→Associations...
then use Alt+F3(or F3) to open files.
Also you can use F4Menu or ChoiceEditor as "Editor for F4" and open files with F4
jeah, the general idea behind CAFE is great. but the program produces a small but noticable 'lag' while changing directories, which i find very annoying.HBB wrote: C.A.F.E is very interesting! It changes windows associations temporarily while it runs. It is also good news that stable (not beta) PortableApps will be available soon for it.
i'd welcome a internal solution also...
Thanks dott, your suggestion is good.
For a few days, I replaced the lister view (direct content viewing) from F3 to Alt+F3 and I tried to associate executables to F3 directly.
This way is new for my fingers, but I hope that they will learn it.
By this new way, I associated most of file types to certain executables in my portable disk. They worked succesfully. But I have encountered a problem. Let me explain the problem in an example:
I am using unzipped version of VLC VideoLAN on portable disk. For VLC, it is possible to open files with the settings (config file) on portable disk by the following statement:
T:\Programs\VideoLAN\vlc.exe --no-plugins-cache --config="vlcrc"
When I create a button on TC and write above statement into text box of "Command:", the files are easily opened by drag and drop. So, no problem...
When I try to associate a video extension (e.g. flv, mpg, .. etc.) to VLC in "Configuration+Edit/View+External Viewers+Associations" and when I write above statement into the text box labeled as "Associate with:", it does not work.
doesn't TC take care of the extra commands for external viewer definition like in "button definitions". If so, why? If it is possible in "buttons", I think that it might be possible in external viewer.
Or, do I have a mistake?
For a few days, I replaced the lister view (direct content viewing) from F3 to Alt+F3 and I tried to associate executables to F3 directly.
This way is new for my fingers, but I hope that they will learn it.
By this new way, I associated most of file types to certain executables in my portable disk. They worked succesfully. But I have encountered a problem. Let me explain the problem in an example:
I am using unzipped version of VLC VideoLAN on portable disk. For VLC, it is possible to open files with the settings (config file) on portable disk by the following statement:
T:\Programs\VideoLAN\vlc.exe --no-plugins-cache --config="vlcrc"
When I create a button on TC and write above statement into text box of "Command:", the files are easily opened by drag and drop. So, no problem...
When I try to associate a video extension (e.g. flv, mpg, .. etc.) to VLC in "Configuration+Edit/View+External Viewers+Associations" and when I write above statement into the text box labeled as "Associate with:", it does not work.
doesn't TC take care of the extra commands for external viewer definition like in "button definitions". If so, why? If it is possible in "buttons", I think that it might be possible in external viewer.
Or, do I have a mistake?
As far as I know, isn't possible.doesn't TC take care of the extra commands for external viewer definition like in "button definitions". If so, why? If it is possible in "buttons", I think that it might be possible in external viewer.
Maybe a BAT or CMD file with the executable and parameters in it could do the job? I didn't test this though.
Alternatively you could ask to the author about add internal commands(especially user defined commands) to the associations dialog.
Hello dott, thank you for reply.
Firstly I must say that my aim was simply to thank you for your F3 opinion, not to ask to you TC features. Probably, I could not succeed to write what I mean.
I hoped there must be a way to do it. But, I understand that "command lines" can not be defined yet in "external viewer definition".
It is not so problem, I will try other ways.
Again, sorry for misunderstanding.
Firstly I must say that my aim was simply to thank you for your F3 opinion, not to ask to you TC features. Probably, I could not succeed to write what I mean.
I hoped there must be a way to do it. But, I understand that "command lines" can not be defined yet in "external viewer definition".
It is not so problem, I will try other ways.
Again, sorry for misunderstanding.