KDE_FULL_SESSION / Open File dialog
René J.V. Bertin
rjvbertin at gmail.com
Thu May 12 09:26:29 UTC 2016
On Thursday May 12 2016 08:57:44 Kevin Funk wrote:
>Well, either way: We need to have *some* input to know whether we should show KDE file dialogs or not. Currently we use the `KDE_FULL_SESSION` env var (which is suboptimal, I agree), but it could be *anything*. It should be a runtime option nevertheless. Not a compile-time one (as you seem to want). User preferences vary.
No, it's not that I *want* it to be a compile-time decision, it's just that that's good enough for me. Ideally you'd add a configuration option (making sure it applies to all existing and future sessions, and also that it's saved/restored properly ;)). But a KDEV_ env. variable like the ones controlling the welcome page or splash screen could do too. They're just harder to document so that users know they have a choice (and also to deploy, on OS X and MS Windows).
One thought though: I cannot check ATM what a KFileWidget looks like when the KDE platform theme isn't loaded, but it currently isn't exactly trivial to deploy that theme and get it to load on OS X. My MacPorts ports for KF5 should take care of that (if you use my Qt5 port and install the FrameworkIntegration FW), but in other builds an option to use KFileWidget dialogs might not have the expected effect?
>
>Note: This is somewhat unrelated to this patch, please discuss that on the mailing list. Let's keep this one focussed on the issue we're trying to fix.
Roger!
R.
More information about the KDevelop-devel
mailing list