Multi Commander > Support and Feedback
Launching of apps associated to file types
pstrg:
--- Quote ---As I said before. You need to enable loglevel "debug" for it to show the error sent from Windows.
MC is not launching foobar2000. MC tell windows to open these file with whatever you have configured with file associations.
MC is forwarding all to Windows. It should be the same as Windows Explorer does. It does the same thing.
I works for me for winamp and other program. FooBar2000 I never tested on that. And I currently do not have the ability to do that
--- End quote ---
Please note that logging was already enabled...
In fact, just in case, tried each of the four Debug settings (Eval, Trace, Result, Begin/End).
In all cases, upon selecting files and hitting Enter, nothing shows up on the debug tab(s).
Mathias (Author):
--- Quote from: pstrg on July 28, 2020, 19:01:07 ---
--- Quote ---As I said before. You need to enable loglevel "debug" for it to show the error sent from Windows.
MC is not launching foobar2000. MC tell windows to open these file with whatever you have configured with file associations.
MC is forwarding all to Windows. It should be the same as Windows Explorer does. It does the same thing.
I works for me for winamp and other program. FooBar2000 I never tested on that. And I currently do not have the ability to do that
--- End quote ---
Please note that logging was already enabled...
In fact, just in case, tried each of the four Debug settings (Eval, Trace, Result, Begin/End).
In all cases, upon selecting files and hitting Enter, nothing shows up on the debug tab(s).
--- End quote ---
That is "Filesystem Log" (Log for Filesystem scanning and such) If you look at the top you see "Application Log"set the loglevel for this to "Debug"
The log for filesystem log you can disable again. It is very verbose and you do not need that.
pstrg:
I appreciate your patience.
Application debug now enabled as well.
After I select a number of files and hit Enter, nothing happens and no new data appears on the log window.
https://i.imgur.com/oZ7HRyT.jpg[/img]]http://imgur.com
Mathias (Author):
Ehh Nothing ? That is not correct.
It should always print out the result code in the log like
"<DATE> <TIME> ShellExecute Error 0"
Did you remove the custom filetype setup you did?
But I don't really know what this will give you. It will probably give you an error code that is sent from Windows that is nonsens.
There must be something with how foobar is registered that is wrong/missing if for now it queue files if multiple files are launched
pstrg:
Looks like something was caught this time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version