Le Sat, 26 Nov 2011 11:42:47 +0000, Thomas Adam <tho...@fvwm.org> a écrit :
> On Sat, Nov 26, 2011 at 12:37:16PM +0100, Dominique Michel wrote: > > Le Fri, 25 Nov 2011 09:18:52 +0000, > > Thomas Adam <tho...@fvwm.org> a écrit : > > > > > On Fri, Nov 25, 2011 at 12:47:06AM -0600, David Fries wrote: > > > > Sending a SIGTERM to FvwmButtons works to gracefully unswallow a > > > > program called stalonetray which is a system tray. Setting > > > > -transient on the FvwmButtons panel is calling XDestroyWindow > > > > and in term causes the programs with items in the system tray > > > > to crash with a bad window error. I'm removing the > > > > XDestroyWindow call and letting all transient > > > > > > Well, I suppose what's happening here is that if an application > > > has registered with a systray which is then killed, then it's > > > probably defined behaviour that those programs will die along > > > with it, although that to me seems buggy behaviour. > > > > It is a buggy behaviour. Such an app must wait for another systray > > app to show up. As example of good behaviour, qjackctl and > > claws-mail work > > It will depend what happens to the application with XDestroyWindow() > -- I was referring to the fact that stalonetray is broken with this, > which is not surprising. That other programs attached to it bomb out > as well does not surprise me, given what happens to stalonetray. Do you know if the developer of stalonetray is aware of this? > > -- Thomas Adam > -- "We have the heroes we deserve."
