j

Results 101 comments of j

With 18b50ac8f5fd553998e54bb1d4c21643986dfa90, command line parsing defaults to file system paths instead of shell paths. Parsing the `%i` parameter (IDLIST) could allow matching the user's choice. See: https://superuser.com/questions/136838/which-special-variables-are-available-when-writing-a-shell-command-for-a-context https://www.geoffchappell.com/studies/windows/shell/explorer/cmdline.htm This *should*...

This can also be changed by `IShellLink::Resolve`

Implementing IExecuteCommand could be another way to get the PIDLs directly. https://devblogs.microsoft.com/oldnewthing/20100312-01/?p=14623

Same issue occurs with file dialogs. Weirdly this doesn't happen when copying from ZIP folders (though drag-and-drop seems to be disabled while this is happening)

Would this be solved by #122?

https://learn.microsoft.com/en-us/windows/win32/shell/datascenarios#dragging-and-dropping-shell-objects-asynchronously

See: https://learn.microsoft.com/en-us/windows/win32/api/thumbcache/nn-thumbcache-ithumbnailcache

https://learn.microsoft.com/en-us/windows/win32/wintouch/troubleshooting-applications

https://learn.microsoft.com/en-us/archive/blogs/murrays/automatic-richedit-hyperlinks (updated) https://devblogs.microsoft.com/math-in-office/richedit-hyperlinks/