| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
window. Actions bound in this context can be executed with the mouse during a move/resize on a window.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
can all be in the same place now woot.
allow actions to specify when they can be used (ShowMenu cant in the OB_USER_ACTION_MENU_SELECTION case)
remove KeyboardMove ad KeyboardResize. Instead, just use Move and Resize and determine if it should be a keyboard move/resize in the code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
add the <interactive> option to them to turn off interactivity
|
|
|
|
|
|
|
|
|
|
more menu cleanups
|
|
menu fixups
move enabled into the 'normal menu item' specific data stuff
|
|
any more.
redo the client-menu plugin to work with the new menu api
|
|
|
|
|
|
|
|
|
|
split the menu into its own file.
|
|
|