Quote Originally Posted by pherthyl View Post
Have you investigated using the native open dialog with QFileDialog and listening for the filesSelected signal? You could just position a preview window beside the open dialog and show the currently selected image.
The thing is that QFileDialog isn't a native dialog - it's customized to, but by trolls(besides it's weak in my opinion), native dialog can be called by QFileDialog from a static method, but it's not emitting anything.
Qt won't help because this behavior is determined by winApi.

I know that I'm loosing lots of goodies by customizing fileDialog, but my application work's on images only so it's a priority to have preview or thumbnails & native dialog opens always in list mode. Imagine that on each file you're opening file dialog, changing view to thumbnails and picking a file then... thumbnails view that can't be set to default is useless, nobody will change it every opened file, in other hand soft for image processing that have no functionality that shows what you are actually opening - i already have one (written view years ago) and i'm ill when i'm using it... it's a priority and it seems that i can't achieve it without sacrificing some native functionalities.

Native dialog is great, there's no discussion here, but it's not supporting applications that are meant to work with images.

In addition, note that windows won't generate thumbnails for all formats supported by qt...

On the margin: I already done custom dialog with scalable preview(that can be turned off), with mode that allows to open multiple files, and thumbnails view (with cache, xml file per directory with generated thumbnails & timestamps, thumbnails generating thread). It fits to my app better than native dialog & it have minimal assumed functionality (maybe it will be enhanced...)so i think problem is solved, at least temporary, but i'm still interested about your opinions...