a debian user reported that jpilot alarms where opened in the desktop where jpilot was started instead of in active desktop. Apparently in KDE alarm opens in all desktop, but I can't try in KDE. It's reproducible on 4.4.
I attach my xfwmrc if needed.
I'm not really sure the bug lies in xfwm but would like to take your advice on this.
Created attachment 1163
Unfortunately, the xfwm4rc file won't be of much help here.
Can you ask the user to to an xprop on the window and post the result?
I cannot reproduce this problem. Can you try playing with the activate_action option? I'm using "bring" here.
It sounds like a dup #2961 and #2837
Hidden options allow you to customize xfwm4 behaviour. They have to be
added by hand to your HOME/.config/xfce4/xfwm4/xfwm4rc file. You may have to
create this file.
How the window manager must react when a window raises itself. When set to
"bring", the window manager to bring the window on the current workspace,
"switch" will switch to the window's workspace, and "none" will simply do
nothing but set the "demand attention" flag on the window.
No news, good news? More than two weeks without any update, closing, it's a dup anyway.
Hmh sorry for the delay, I had two weeks without net access when moving to a new flat.
I didn't know about the hidden option, but it doesn't work anyway. Nor "bring" or "switch" work. In wm tweaks the two boxes are checked (focus stealing prevention and ICCCM focus hint).
Well it works for me. What version are you using exactly?
Ok, I double checked. Indeed, the alarm window is a transient for the jpilot window, so it's properly set on the same workspace. This is not a bug in xfwm4 and it will not be fixed. Why not fixing jpilot instead?
Humm, maybe this could be more relaxed on the xfwm4 side too, let's see...
Ok, I've committed a change that allows transient to be made sticky independently of their parent windows.
It looks a bit odd IMHO, but... it's in svn.