I've been wanting to have a middle- or right-click menu
but I'm currently using a WM which leaves popup menus
to other programs. So I've added generic command
support for middle-clicking anywhere on the pinboard
and right-clicking anywhere on the pinboard except on
icons.
The attached patch implements this, with room for
expansion for extra buttons (change the size of
o_pinboard_user_cmd[] and add the corresponding items
to Options.xml).
Implement pinboard click commands
Logged In: YES
user_id=40461
Should this test be the other way around?
if (spawn_user_command (event->button))
forward_to_root(event);
Do we really need two custom commands? Button-2 is reserved
for the window manager, so having a command for that is fine
if the WM doesn't need it, but passing button-3 clicks is
only for backwards compatibility - on modern systems the
pinboard menu should be opened in all cases. Only having one
option would also reduce clutter in the options box.
The option should probably be in the 'pinboard' section, not
'compatibility'.
Logged In: YES
user_id=294680
Whoops. Yes, it should be inverted.
I've allocated two custom commands because that's what I'm
using: window menu and apps menu. Ctrl+Button-3 could always
open the ROX menu, I suppose.
Moving the options is trivial. Should I regenerate the
patch, I'll do that.
As for extra buttons: I should mention that I'm using a
mouse which has five others (nos. 6 to 10: wheel left &
right, side buttons, "task" button) which could have
commands assigned to them. Wheel up & down are... less
useful for this, I think, and they're already used here anyway.
Logged In: YES
user_id=40461
I think an patch for a single button command would be OK. If
you want to do more complex stuff, you can always run a
separate process that selects for events on the root window
and has its own configuration.
This is how "deskmenu" works, for example.