because if one timestamp is reused for activating window A and then
immediatelly window B, and A will want to set focus to one
of its subwindows after receiving WM_TAKE_FOCUS, and will lag a bit,
it will actually set the focus after B, and will win. Fixes#71704.
If somebody still gets the warning, I'd be interested in the backtrace.
svn path=/trunk/kdebase/kwin/; revision=278208
don't use Workspace::activeClient() as the active client, but instead
the most recent should_get_focus client - that may make a difference
if a window was just activated, but the matching FocusIn event that'll
make it to be activeClient() wasn't yet processes. Visible with apps
that show several windows at the same time after startup.
svn path=/trunk/kdebase/kwin/; revision=270831
hidden, otherwise it could attempt to restore the focus back to this client.
CCMAIL: 66926-done@bugs.kde.org
svn path=/trunk/kdebase/kwin/; revision=263383
the focus and just are there. Therefore, as a part of focus stealing
prevention, let's also block raising of windows. Also added special
request for Kicker, as taskbar requests for raising should be obeyed.
(Not that this does anything to KPassivePopup.)
svn path=/trunk/kdebase/kicker/taskmanager/; revision=255070
Luboš Luňák