Hello!!!

well... I will explain my problem with one example:
- Focus stealing prevention at Medium or Extreme, does not matter.
- Skype open and at background
- Currently watching webs or writting an email at firefox or maybe writting at ssh session, or programming...
- Someone writes to me at skype
- Then the taskbar highlights the skype "icon"... the skype window is not at the front.. it keeps at the background, or minimized... but:
- my writting is stopped and I really do not know where are my letters going to... I guess my keyboard is going to taskbar itself, neither skype.
- As I use transparency at inactive windows, my active firefox where I was writting is now inactive and getting transparency... my keyboard is not writting to firefox... I must left click at firefox window to get it active and with focus again.

If you have a look at: http://docs.kde.org/development/en/kde-workspace/kcontrol/windowbehaviour/index.html

Windows that are prevented from stealing focus are marked as demanding attention, which by default means their taskbar entry will be highlighted. This can be changed in the Notifications control module.

Ok... I go to system configuration/notifications........ have had a look at all the possible items (guess the one is KDE workspace) and disabled all events with "highlight at taskbar" flag checks.... but nothing.

I cannot get this highlights off!!!

I cannot understand, with focus stealing prevention extreme, which way could I configure to prevent an incoming skype message just deactivate my current active window where I am writting, and I need to left click at it to continue because of the taskbar!!!

Could you help me!?

Thanks!!

Moved to the KWin forum, as it is responsible for mediating the attention hint, and manages focus stealing - it would seem that this isn't working properly in this case (although Skype could be doing something nasty here).

Since KWin apparently sets the urgency hint (taskbar starts to blink) and the window is not moved to front, that means it does not activte the window (due to the FSP settings) what also means it will not pass it the input focus what -likely- means, skype just pulls that itself.
It's unfortunately anything but trivial to figure which window does have the input focus (esp. since you cannot use konsole for that)

Only thing i can suggest atm. is to add a window rule for skype that passes it a lower focus stealing prevention.
Unfortunately there seem issues with this as well, since skype seems to alter the WM_CLASS at runtime ...

Hi!

Thanks for your answers

I have created a rule for windows from "skype" with focus stealing prevention at extreme, but just the same behaviour...

Maybe I am a bit confused, but is there a chance the real problem is the taskbar stealing focus due to the "urgent attention hint", and not the skype window?

Regards!

supposing the rule is applied, the correct strategy would be "none", ie. the direct opposite.
i assume that skype tries to activate itself (denied) and just grabs input focus, completely bypassing the WM, interacting with X11 directly - iow, focus stealing cannot be prevented, as skype plays WM (there's really no way - clients are expected to behave, showing the age of X11