| Age | Commit message (Collapse) | Author |
|---|
|
|
|
variable was getting set from all kinds of events like motion notify. totally not reliable. now it works all nice.
|
|
|
|
|
|
|
|
menu if it changes. it does this by closing/opening the menu.. thats about the best we can do tho with this menu code without huge changes
|
|
|
|
renaming.
let you highlight disabled menu entries, they just aren't runable of course, and add the activedisabled theme element for these entries.
add the all desktops button picture to "All desktops" in the client menu
update the themes for the new element, and some changes to make things more readable-better contrast.
CLEARLOOKS-OLIVE is now DIFFERENT FROM THE 3.4 BRANCH SO DON'T RE-RUN THEMETOXML ON IT :( :(
yeah.. i think that is everything?
|
|
|
|
key binding.
change how the first menus are placed. place them like other people place menus. maybe this is good, maybe it is bad, we will see..
|
|
like menu titles and what not, they are only for strigns oenbox provides.
|
|
even in root menu and stuff
|
|
2) let separators have labels, when they have a label, then they will appear like a menu title used to
so if you want a menu title, you use a separator in the menu itself at the top
more style work may be needed
|
|
|
|
all related to _NET_WM_USER_TIME and focus stealing prevention
a) add launcher startup notification. this means when you run something from
the openbox menu or a key/mouse binding, that startup notification will go
on in openbox and other applications like your panel or something
b) add the _NET_WM_USER_TIME property for windows
c) use the _NET_WM_USER_TIME data and startup notification to prevent focus
stealing.
d) cookie party !! ! all are invited.
e) oh yeah, and pass around timestamps for a lot more things. like, when you
run an action, send the timestamp for the event that is running the action.
this is important for startup notification. this also affects menus.
f) yes.. cookies..
would it be a good idea to disable focus stealing prevention if a window takes
too long to load? i mean.. maybe after a certain length of time, a user can't be
expected to not do anything in any other windows, but would they still want the
new application to focus then? HMM. open question i guess..
|
|
|
|
--help output to not include version output.
|
|
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
|
|
|
|
support reconfiguring throughout the entire codebase.
|
|
mask icons instead of teh bullet color, and set it based on selected/disabled/normal like the text.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
they are shown.
crash fix in client_menu
|
|
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
|
|
work, on to plugins next.
|
|
fix a possible crasher where a callback was called with a different menu.
|
|
split the menu into its own file.
|
|
make workspace changing a grabbed/interactive process like focus cycling is, with the popup and all.
this is some hot shit.
|
|
clear no one gives a fuck what I think and no one else wants a window
manager that doesn't suck the same balls as every other window manager.
|
|
Don't talk to me about menus.
|
|
No one cares what I think anyway.
If the menu navigation isn't EXACTLY FUCKING RIGHT I WILL REMOVE IT
AND SOME OTHER POOR FUCK CAN PUT UP WITH ALL THE FUCKING BULLSHIT.
|
|
|
|
|
|
FIFO menus are the only plugin that takes advantage of this.
Example:
<menu id="root" label="Openbox 3">
<menu id="fonk" label="fonk" plugin="fifo_menu">
</menu>
</menu>
This creates a FIFO ~/.openbox/fifo_menu/fonk to which you can send
menus to. The menus sent to it must be like
<fifo>
<item>
etc...
</fifo>
I think. If my memory serves me right.
It is all hideous, but I just wanted to experiment and see if it was
possible.
|
|
make the ObMenuEntryRenderType a standard enum instead bitflags
|
|
less includes in headers for less rebuilding on changes
|
|
|
|
|
|
time, and making them act like gtk menus and * menus do, where you can click and drag and release to select something as well as click-release to elave it open while you search around the menu
|
|
|
|
|
|
Add "client_menu" to pluginrc to use.
|
|
add config options to the rc3 for the dock.
create a window_map, add DockApps to the ObWindow types, use the window_map for translating windows into objects for event handling (only one lookup now) and remove the old maps (client_map, menu_map).
|
