Stop window from raising on new message?

[Penumber]

I'm running aMSN in Linux, and I'm trying to stop it from raising chat windows to the foreground whenever I get a new message (though it doesn't steal focus, thankfully). I can't find any kind of setting in preference, and I can't pinpoint exactly where in the code the call to raise this chat window happens. I was hoping someone could point me to a solution for this or the method/file in which the raise happens; it's ever so annoying to me.

Sorry for the bother, and thanks in advance.

[square87]

Hello Penumber.
Try with:
account -> preferences -> session -> When a new message arrives I want it to be: minimized/iconified
Bye

P.S. it's not a bother

[kakaroto]

Hi,
this shouldn't happen... the 'when a new message arrives' setting is very confusing.. read here for more info : http://www.amsn-project.net/forums/viewtopic.php?p=16665#16665
in other words, it shouldn't happen... maybe you have a plugin that does that or something.
which version are you using ?

[malteo]

I'm sure he is using compiz and this is the dreadful "jumping window" bug: http://www.amsn-project.net/forums/viewtopic.php?t=1160

BTW, I experience this bug too

[Zalbor]

Yes, it's compiz. I used to have it too.
I installed Beryl and it's all fine now!

[faustix]

Yes, it's compiz. I used to have it too.
I installed Beryl and it's all fine now!

Hi,
I'm using fvwm2 windows manager in Fedora 7 and
I had the same problem. I think the problem is that
not all the windows managers support the XUrgencyHint
or handle it the same manner.
I found an example program at http://modeemi.fi/~tuomov/ion/misc/urgent.c
When it runs on a iconified xterm (ex: sleep 10 ; ./urgent )
the xterm deiconify and the mouse pointer goes on it, as when a message comes in amsn.

So my crude workaround, as I'm used to download and compile the source code
from the SVN repository, was to comment out the code in utils/linux/linflash/flash.c (line 194)
compile and install.

Code:

int setUrgencyHint(Display *display, Window window, int flash) {
  XWMHints *hints;

#if 0
  hints = XGetWMHints(display, window);
  if (hints != NULL) {
    if (flash)
      hints->flags |= XUrgencyHint;
    else
      hints->flags &= ~XUrgencyHint;
    XSetWMHints(display, window, hints);
    XFree(hints);
    return 1;
  }
#endif
  return 0;
}

That restores for me the old amsn beaviour when messages arrive:
- open chat window minimized with flickering icontitle.

Bye!

[kakaroto]

it's probably a bug in your window manager, if it support the demands_attention atom, then it should tell us that it does.. the urgency hint is ONLY executed if the window manager says that it doesn't support the demands_attention. Also, the urgency hint shouldn't (afaik) raise the window...
glad you fixed it.

[faustix]

it's probably a bug in your window manager, if it support the demands_attention atom, then it should tell us that it does.. the urgency hint is ONLY executed if the window manager says that it doesn't support the demands_attention. Also, the urgency hint shouldn't (afaik) raise the window...
glad you fixed it.

Hi,
I don't think it's a bug, instead
reading more deeper in the fvwm2 docs I found:

Further additions are support for client-side colormap installation (see the .SM ICCCM for details) and the urgency hint. Clients can set this hint in the WM_HINTS property of their window and expect the window manager to attract the users attention to the window. Fvwm has two re-definable functions for this purpose, "UrgencyFunc" and "UrgencyDoneFunc", which are executed when the flag is set/cleared. Their default definitions are:

Code:

    AddToFunc UrgencyFunc
     + I Iconify off
     + I FlipFocus
     + I Raise
     + I WarpToWindow 5p 5p
    AddToFunc UrgencyDoneFunc
     + I Nop

I think it's quite clear what will be the behaviour of the window manager,
even without knowing the config syntax, isn't it?
Deiconify, GetFocus, Raise and Go to the upper left corner of the window...
hehe found the problem
So, a less crude solution, without touching the amsn source code was
to add in my  .fvwmrc the following line:

Code:

DestroyFunc UrgencyFunc

Maybe that can be useful to other people...
Bye!

[kakaroto]

well, I still consider it as a 'bug', it doesn't act as other window managers, it's the only WM that does that, so it shouldn't... also, notice that as I said we only send the urgency hint if the WM doesn't support demands_attention, so it seems your WM doesn't support it or supports it but doesn't let us know it does...

Anyways very good finding, and thx for sharing the info with everyone.

[danielrigano]

Installing Beryl  is also a good solution.

[rowanparker]

Installing Beryl  is also a good solution.

How? It still does it for me?
Please share