On 25 March 2012 16:46, Robert Parlett <r.parl...@gmail.com> wrote: > The naming of the fields in the overlapping structs XAnyEvent and > XDestroyWindowEvent is highly misleading, and I can easily see how one > could write "Event.xany.window", thinking you were getting > "Event.xdestroywindow.window", but in fact were getting > "Event.xdestroywindow.event".
I think I'll just go with changing the event to check for xdestroywindow.event and leave everything else as-is. That seems the best approach. As far as stalonetray goes, it is very odd in its approach to managing the tray icons -- and it's only that reason which has caused it to be problematic, not just in FVWM but other window managers. Please note that I do not want bugs/design flaws/whatever you choose to call them with stalonetray, to be conflated with other problems in FvwmButtons: that you found one very odd case where this is triggered is not indicative of allowing stalonetray off the hook. It is fundamentally broken. -- Thomas Adam
