We run by default with a panel (default gnome-panel) and then run Openbox without any panel if one cannot be found. - Adds a fallback session for if a panel (default gnome-panel) not found. - Removes notifications as a requirement. Seems to be a legacy thing judging from the ubuntu .session files. Notifications are being provided by notify-osd on modern systems, and you can't check for its presence in gnome-session (gnome-classic.session always fails because it looks for it, so ubuntu falls back to gnome-fallback.session).
…itorPlace for per-app too
…g a position in it.
…for per-app settings (bug #5180)
…bug #5179) splits client_setup_decor_and_functions() into 3 functions. 1. add client_setup_default_decor_and_functions() - called from client_get_all() to get the maximum decor/functions that will be available for use by the client. 2. add client_setup_decor_undecorated() - sets up the client's undecorarted decor if the flag is set by the per-app settings or session state. - we do this before setting up the frame so the frame reflects the window as it should be when getting placed. 3. client_setup_decor_and_functions() - calls the above 2 to perform the same functions as before. - added to client_apply_startup_state() so that we can ensure it was run fully at least once in the mapping process, since it is not called in client_get_all() anymore.
It will get the primary monitor if there is not monitor under the pointer. But assert so it's clear something went wrong if this does happen. Note that there was previously no check for the return value even though the comment claimed there should be.
libobrender uses ObtPaths stuff, so it needs to link in libobt.
…gs (bug #4937)
…bug #4889) The attached patch adds three theme options with backward compatible defaults: undecorated.border.width defaults to border.width window.undecorated.active.border.color defaults to window.active.border.color window.undecorated.inactive.border.color defaults to window.inactive.border.color
Don't assume old tree is non-null and start rebinding it.
…ast click was Bug #5152 - "mouse double-click time is too low by default - 200ms" We only use the doubleclick in one place in the default configuration, for doubleclicking titlebars to maximize windows, so any negative impact of increasing the timeout should be minimal, especially with the addition of requiring the two clicks to be in the same place. Doubleclicks are hardcoded to occur within 8 pixels for now, it doesn't seem worth it to add a config until someone complains. A possibility is using the drag threshold, but some people have that set very low so it could be hard to doubleclick then.
…3.0+ support. Yay they did something nice and made it easier for other window managers to be used. How unexpected and pleasant.
Showing prompts causes messages to be created which causes the glib message handler to abort(). Save the messages and show them when done all other processing for the current event.
Startup scripts should export "XDG_MENU_PREFIX=kde-4-" but they export "XDG_MENU_PREFIX=kde-".