View Single Post
Old 04-21-2016, 09:41 PM   #29
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,450
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Quote:
Originally Posted by DiapDealer View Post
Any merit to subclassing QFileDialog to avoid the native filopen dialog? Or would the arbitrary extension code still fire?
Yeah you can use the Qt file dialog instead, as far as I know, that does not load shell extensions. However, it is functionally much more limited than the native file dialog. calibre has an environment variable that you can set to disable use of native file dialogs.

It is on my todo list to someday create a standalone windows executable that does not have any dll dependencies (apart from standard windows ones) that communicates over stdin/stdout and can run windows file dialogs -- that's pretty much the only way I can see to robustly workaround this problem.
kovidgoyal is offline   Reply With Quote