[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 187718] Focus screwed up after closing emacsclient window (with
From:       Alain Knaff <kde () kde ! lka ! org ! lu>
Date:       2010-06-02 20:25:23
Message-ID: 20100602202523.E2A2740E51 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=187718





--- Comment #11 from Alain Knaff <kde kde lka org lu>  2010-06-02 22:25:11 ---
> on the NETWM level there's actually just this one client message to claim
> *activation* _explicitly_

If there is only one client message to claim activation, why are there so many
different levels of focus prevention ("low", "medium", "high")?

> there's however a difference between claiming active state and input focus,
> latter is done via XSetInputFocus and implicitly requires activation - this is
> what applications are usually supposed to do as it is what they actually want.

What is the difference in purpose between asking for activation and asking for
focus?

And why would a (non WM) application ever explicitly ask for focus (rather than
wait until it is given focus)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]