similar to: [PATCH][0.9] Make bool CompWindow::isFocussable Wrappable

Hi, in a plugin I am developing with some other people (namely: tabbed window grouper), we want to paint a glow like effect around the windows. This is done by adding the glow as "second decoration" around the window decoration. The question now is: How can we communicate the fact that there is a second set of decoration properly to other plugins so that window damaging and

I've been thinking about removing all existing notification functions in favor of just having functions that apply changes. This is better as it allow each plugin to execute something both before and after the change has been applied. Example: Instead of wrapping a windowStateChangeNotify function you would wrap a changeWindowState function static void pluginChangeWindowState (CompWindow *w,

I am working on exposing events to external apps via the dbus plugin I found that I really wanted extra Notify Procedures so that I didn't have to do too much direct access to xlib (If I understand rightly, plugin developers shouldn't have to do too much xlib work inside the plugins) I added Create, Destroy, Map, Unmap, Minimize and Unminimize Hopefully this can be included as I know a

A new compiz release 0.7.8 is now available from: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz which can be verified with: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz.sha1 7b8a67b5d5b4aa6a33fcf60691bfae757768ffa3 compiz-0.7.8.tar.gz http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz.sha1.asc (signed by Danny

Hi I just tried out the new 0.1.0 release of beryl. Generally I do like the compiz fdo version, because I like the gconf integration and the metacity theme support in gwd. Also I think their configuration system is a complete mess, this beryl settings manager is completly bloated in my opinion. Anyway, I noticed they have quite a lot of plugins. While I found most of them nothing special, the

Here's a quick patch to have either horz or vert (instead of both) maximized windows honor the "ignore" option: --- src/window.c +++ src/window.c @@ -4012,7 +4012,7 @@ constrainNewWindowSize (CompWindow *w, if (d->opt[COMP_DISPLAY_OPTION_IGNORE_HINTS_WHEN_MAXIMIZED].value.b) { - if ((w->state & MAXIMIZE_STATE) == MAXIMIZE_STATE) + if (w->state

About a month ago, David made a commit to wobbly to the spring engine which has introduced some bugs. They are hard to explain so bear with me. In a sense, the wobbly plugin does not seem as smooth as it used to be and the windows jerk all over the place. For example, I sometimes notice that when I move a large window (around 2/3 of the size of the desktop window), If I moved it down, the top of

I wrote this quick patch because I want plugins to be able to communicate with each other with events. Using the option values to communicate with each other is a bit cumbersome if you want to monitor for changes or do anything which requires events. It is just a small patch and works in the compiz way (ie by wrapping the core event). Some potential events that I can think of at the moment are

My recent work on Compiz-scheme has brought to my attention several problems preventing a real compiz extension language. Note that when I refer to an extension language, I am not referring to the ability to add plugins in some other languages, but more of something in the vein of emacs lisp. The major problem right now is extension languages are locked in to one plugin and what core exposes.

Me and Dennis Kasprzyk changed CompRect to be more intuitive and easily replace XRectangle use. This patch changes CompRect and whole Core. Thanks for attention. -- Eduardo Gurgel Pinho (GELSoL-UFC) (Gentoo) Linux User #415930 http://edgurgel.wordpress.com http://alu.dc.ufc.br/~eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, Recently i have worked on re-writing beryl's transparent cube, and ported 3d plugin to compiz. I'm attaching a patchset here that includes the transparent cube patches (i'll post the 3d plugin when i fix some problems that didn't happen in beryl). Patching order: btf-ftb.patch, clip-planes.patch, plugin-events.patch, cube-paint-order.patch, transparent-cube.patch. Special

Taking David's example further, here is a first try: id | name | description | more info -----+---------+-------------------+----------------- 6 | Inset | An inset element | just one element 8 | Stories | Another element | another element : with 2 lines, without : colons on the left. 9 | Other

Hi all, attached is a patch which extends the window resize notify function: Instead of just passing the CompWindow*, additionally the resize difference information is passed (difference of position, width and height). Originally, I wrote this one for Beryl as we needed it for the group plugin, but I think it makes sense that Compiz also has this for the sake of plugin interoperability;

I was writing a simple plugin a while ago which just sets the paint values on inactive windows. The plugin is very simple and the main part is below. When I load this plugin it blocks dbus and fuse plugins so that they only reply to requests when the active window changes. Is there anything obvious here that would cause that? static Bool inactivePaintWindow (CompWindow *w, const

A new compiz release 0.7.4 is now available from: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.4.tar.gz which can be verified with: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.4.tar.gz.sha1 a204d9b70ac8abfb037ca3402452aa055f4aab71 compiz-0.7.4.tar.gz

Here's a patch to wobbly.c to handle edge snapping with multiple outputs... Also, I tweaked the window edge snapping to include dock window types, to support the case where dock windows may be on the inner edges of multiple monitors (and thus currently ignored as struts in the output workarea setup). I personally think we should include these "inner" struts when calculating the

hi, I saw that Mike Dransfield tried to port 'state' plugin from beryl. What does it do? It should be able to place windows, based on name, class etc., to specific viewports. I recently converted to compiz window manager from WindowMaker (used it for 8 years), and I miss automatic 'pinning' of specific windows to particular workspace (or viewport in this case). Mike's

Hi, This patch fixes a leak when creating fragment functions in some of the plugins. The leak happens when there is a plugin that uses a fragment program with parameters and texture units on only a subset of windows. During screen painting, the allocated param and unit change across windows in the patched plugins, which (because of the mismatch with the previously created and stored function)

From: Kristian Lyngstol <kristian@beryl-project.org> Avoids focus jumping from one screen to another. --- include/compiz.h | 4 ++-- plugins/rotate.c | 2 +- src/display.c | 38 +++++++++++++++++--------------------- src/event.c | 6 +++--- 4 files changed, 23 insertions(+), 27 deletions(-) diff --git a/include/compiz.h b/include/compiz.h index 4c72dd3..f882b84 100644

Hi, I'm getting a lot of warnings like this one: (gtk-window-decorator:8442): Wnck-WARNING **: Unhandled action type (nil) Does anyone else see these warnings or know what causes these? Also, it seems that this "lost textures" bug https://bugs.freedesktop.org/show_bug.cgi?id=10789 usually happens only when these warnings are spitted out, so the bug is probably related to these