Custom Open/Save Dialogs
-
wrote on 22 Mar 2011, 12:02 last edited by
I didn't see any Examples for Open Save Dialogs, could somebody upload a good example, using all codes, rather than Qt's built-in Save and Load Functions? I'd love to learn that, to get some extra experience, =). I'm pretty sure you can make your own custom built, from ground up Save/Load File Dialogs using Qt, =).
-
wrote on 22 Mar 2011, 12:06 last edited by
Sure you can. The sources for the Qt versions would be a great starting point. Also interesting are the QFileSystemModel and the different view classes, of course.
-
wrote on 22 Mar 2011, 12:08 last edited by
You can also take a look at Qt's non-native dialogs. Each dialog has an "QFileDialog::DontUseNativeDialog" option and you should find the corresponding code somewhere in qt/src/gui/dialogs. Just my two cents;)
-
wrote on 22 Mar 2011, 12:23 last edited by
[quote author="unclewerner" date="1300795720"]You can also take a look at Qt's non-native dialogs. Each dialog has an "QFileDialog::DontUseNativeDialog" option and you should find the corresponding code somewhere in qt/src/gui/dialogs. Just my two cents;)[/quote]
Thanks, =).
-
wrote on 22 Mar 2011, 12:25 last edited by
[quote author="Andre" date="1300795573"]Sure you can. The sources for the Qt versions would be a great starting point. Also interesting are the QFileSystemModel and the different view classes, of course. [/quote]
I'm getting this message here:
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/rick/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.Why am I getting that?? No matter what I do, I get that error message. I've seen that before, founds results, but nothing matched up to what I seen.. It's weird. Is that just a KDE thing, and something I shoulldn't worry about, or is that a bug that should be sent to Qt?
1/5