Multi Commander > Support and Feedback
Quicklook - nearly works
Mathias (Author):
--- Quote from: Jungle on February 13, 2024, 07:15:57 ---I think that the easiest way would be to allow external app in the preview setup.
Another way - events. Multiple times I wanted to suggest this feature but I'm not sure it's worth the efforts. The point is to allow executing scripts/UDC on certain events like MC start/exit, change file focus, opening/closing tabs, begin/end file operations etc. But I don't think it would be useful.
--- End quote ---
Also been think about some event system to hook into. However there are so many situation that cause issue. specially it depends on what the "script" would do.. And it is also hard to limit what script function can be used to avoid issue and so..
So so far nothing yet since it is very complicated to implement. and I'm not sure many will use it either.. so might be waste of time..
jfmoyen:
--- Quote from: Jungle on February 13, 2024, 08:42:09 ---
--- Quote from: jfmoyen on February 13, 2024, 08:04:03 ---Now of course I have no idea how they do it.
--- End quote ---
I've taken a look at the sources, and from what I've seen and understood, QuickLook constantly monitors active window and tries to get selection from it if the window type matches supported managers (explorer, dopus etc.)
--- End quote ---
I see, so the "issue" (if it is an issue) should be fixed from QL side then, by having it watching more managers...
Jungle:
--- Quote from: jfmoyen on February 13, 2024, 14:12:07 ---I see, so the "issue" (if it is an issue) should be fixed from QL side then, by having it watching more managers...
--- End quote ---
It's not an issue. Unfortunately, adding custom file manager support can't be done by creating independent dll. This would require to change QuickLook.Native project. But the first impression makes me think that adding MC support to QL shouldn't be hard for someone who has Visual Studio installed.
Matthias515566:
--- Quote from: Mathias (Author) on February 12, 2024, 23:19:52 ---crash report
--- End quote ---
There is no crash report because the MultiCommander instance is terminated without any message. The window closes, and the executable is terminated without any message. I have no preview software installed in Windows, and some services may be disabled. I use Adobe Reader and ABBYY FineReader for PDFs. It would be better for MultiCommander to operate independently and not rely on Windows features that may be disabled by users.
Mathias (Author):
--- Quote from: Matthias515566 on February 15, 2024, 05:56:00 ---
--- Quote from: Mathias (Author) on February 12, 2024, 23:19:52 ---crash report
--- End quote ---
There is no crash report because the MultiCommander instance is terminated without any message. The window closes, and the executable is terminated without any message. I have no preview software installed in Windows, and some services may be disabled. I use Adobe Reader and ABBYY FineReader for PDFs. It would be better for MultiCommander to operate independently and not rely on Windows features that may be disabled by users.
--- End quote ---
Maybe you turned it of. Becuse normally a crash report is sent and a dialog shown with a crash ID if MC is just terminated..
All windows have Preview software installed... A lot of them are built from microsoft. If you can show preview in Windows Explorer you have them installed, MC uses the same preview handlers..
Both AdobeReader and FineReader is normally installing its own Preview Handler for PDF.. So then MC is using that via the WindowsPreviewHandler API..
If MC would not use built in features would be a waste. Why invent the wheel again?. It would also take enormous amount of extra work. Parsing and rendering for example PDF are a a very huge and complex task. It is a project that is as big as the rest of MC.
It is just really not possible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version