rclick option for clock only works with mouse, not pen

[GoogleCodeExporter]

Very weird issue here, I set up a rclick command for the clock which works 
fine, UNLESS I try to click it with the Wacom Pen (right click). The Wacom 
driver emits this event from the device, remapped. Best I can do is give you 
what xev | grep -iC 4 button returns. When I click with the touchpad (emulated 
two finger click):

ButtonPress event, serial 40, synthetic NO, window 0x1a00001,
    root 0xaa, subw 0x0, time 6008095, (105,115), root:(106,137),
    state 0x0, button 3, same_screen YES

ButtonRelease event, serial 40, synthetic NO, window 0x1a00001,
    root 0xaa, subw 0x0, time 6008195, (105,115), root:(106,137),
    state 0x400, button 3, same_screen YES

With the pen:

ButtonPress event, serial 40, synthetic NO, window 0x1a00001,
    root 0xaa, subw 0x0, time 6062569, (136,95), root:(137,117),
    state 0x0, button 3, same_screen YES

MotionNotify event, serial 40, synthetic NO, window 0x1a00001,
    root 0xaa, subw 0x0, time 6062585, (137,95), root:(138,117),
    state 0x400, is_hint 0, same_screen YES

<MOTION EVENTS IN BETWEEN, AS OPPOSED TO MOUSE>

ButtonRelease event, serial 40, synthetic NO, window 0x1a00001,
    root 0xaa, subw 0x0, time 6062757, (1278,777), root:(1279,799),
    state 0x400, button 3, same_screen YES

tint2 is the only application that exhibits such behaviour.

Original issue reported on code.google.com by cedric.s...@gmail.com on 2 May 2011 at 4:00

[GoogleCodeExporter]

The problem is that the press occurs at (136,95), the release at (1278,777) -- 
most likely outside the clock. There is a bug, but not in tint2.

Original comment by mrovi9...@gmail.com on 4 Feb 2015 at 10:26

• Changed state: Invalid