And as I see it, I found it kind of silly to hack in a KDE aspect.
-原始邮件-
发件人: "Leslie Zhai"
发送时间: 2014/6/1 15:17
收件人: "Thomas Lübking" ; "kde-devel@kde.org"
抄送: "Daniel Nicoletti" ; "jeffbaich...@members.fsf.org"
主题: Re: PolicyKi
Yes, sometimes the AuthDialog is only transient top of its parent :)
BUT sometimes it is not active...
Emm, modal window is not a good design, I argue that KDE might not use it.
On 2014年06月01日 17:24, Thomas Lübking wrote:
On Sonntag, 1. Juni 2014 09:16:46 CEST, Leslie Zhai wrote:
so there is
On Sonntag, 1. Juni 2014 09:16:46 CEST, Leslie Zhai wrote:
so there is NO Apper assoicate WID for AuthDialog constructor.
2. KWindowSystem::forceActiveWindow sometimes worked BUT ...
Sometimes it FAILED to force active window to act like modal
one
The window is not modal, since it's not tra
Hi Thomas,
Thanks for your reply :)
1. it is NOT a bug about Apper or QJade.
Because Apper and QJade uses PackageKit-Qt, a Qt bindings for
PackageKit. When it calls installPackage function of PackageKit-Qt,
there is pk_transaction_obtain_authorization function in PackageKit to
call PolicyKit
On Freitag, 30. Mai 2014 05:09:58 CEST, Leslie Zhai wrote:
Hi KDE developers,
My colleage reported a bug to me, it is about PolicyKit1-KDE AuthDialog
UI behavior issue, the AuthDialog could not show as TOP_LEVEL
That's called "_NET_WM_STATE_ABOVE" - "toplevel" usually refers to a window
with
Hi KDE developers,
My colleage reported a bug to me, it is about PolicyKit1-KDE AuthDialog
UI behavior issue, the AuthDialog could not show as TOP_LEVEL when
installing some App via Qt frontend of PackageKit, for example, Apper or
QJade https://github.com/AOSC-Dev/QJade
So I simply added setWindo
