Comment 2 for bug 404564

On Mon, 17 Aug 2009, hasi wrote:

> I am not a developer at all. However, can't you do the same thing the
> old versions did?

I could, in theory, but that would be troublesome. It depends highly on
the underlying window manager being known, and using sometimes different
tricks based on the currently running window manager, so it is not really
ideal. My goal here is to have it be more robust, as well as
WM-independent, so that it will "just work" no matter if you are using
GNOME, KDE, e17, or fluxbox (or any other EWMH compliant WM, of which
there are many).

> For me this is actually a quite important feature, especially since I am
> using the task panel in "auto-hide" mode, where clicking on the systray
> icon is not a convenient alternative.
>
> BTW, thanks for working on this important application. I've been using
> the "old" alltray (v0.69) for quite a while now -- first with KDE 3.5,
> then with KDE 4.1 through 4.3. In all the KDE 4 versions (don't remember
> about KDE 3.5), catching the execution of the "close" button does not
> even work flawlessly with v0.69: in many cases, the applications close
> anyway (I am mainly using thunderbird and sunbird).

Does AllTray 0.70 (Jochen's last release) work any better for you?

> --
> Close button support in AllTray trunk
> https://bugs.launchpad.net/bugs/404564
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in AllTray: Confirmed
>
> Bug description:
> Intercepting close-button does not work in trunk; this needs to be fixed. However, the available options to fix this are unclear, and I'm not sure how to proceed. Being that this bug blocks the 0.7.4dev release, I don't know if that release will be coming on-time or not. Any help with ideas is welcome. The goal is to find a way to do this that is portable between window managers and application software, and does _not_ interefere with the operation of things like drag-and-drop and so forth.
>
> Optionally, you (the community) could decide that this is not a killer feature, and the release will go forward as otherwise planned. But I won't do that without some form of consensus.
>