Hi All,

I got a question that only tangentially relates to FVWM, but I could not
think of any other place to ask for advice.

I'm writing a small standalone tray application "stalonetray". In recent
release I added an ability for users to send "fake" clicks to icons from
command line. However, as I was told by one of stalonetray users, and
was able to reproduce myself, not every application's icon responds to
such clicks. I tested if those icons respond to FakeClick from FVWM and
they do. Looking at FVWM sources I could not find any differences
between its code to send button events and mine (in fact, I borrowed
some ideas from FVWM code; thanks!).

One of such applications is stardict which uses GTK. After looking at
GTK sources I realized that GTK filters out ButtonRelease events with
send_event == True. However, after running xev against stardict icon I
noticed that if I execute FakeClick from FVWM, then in addition to two
synthetic events -- ButtonPress and ButtonRelease, which I also observe
when I execute a fake click from stalonetray, there is also a third
non-synthetic ButtonRelease event which does not get filtered out by GTK
and hence stardict icon responds to FakeClick.

Does anyone on this list know the source of this third non-synthetic
event? Any hints would be greatly appreciated.

-- 
:wbr
Roman

Reply via email to