similar to: Re: compiz: Changes to 'master'

With raise_on_click disabled, I wanted to be able to raise a window with a button click sometimes. It seemed logical to do something like the lower window key binding. So I did it. It was quite simple, but here is the patch anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 3680 bytes Desc: not available

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

--- include/compiz.h | 17 ++++++- metadata/core.xml.in | 7 +++ src/display.c | 5 ++- src/event.c | 130 +++++++++++++++++++++++++++++++++++++++++++++----- 4 files changed, 143 insertions(+), 16 deletions(-) diff --git a/include/compiz.h b/include/compiz.h index dd34f00..abb1169 100644 --- a/include/compiz.h +++ b/include/compiz.h @@ -26,7 +26,7 @@ #ifndef

Here are my patches to add edge + button functionality. I still feel that there is a problem with gconf, but I have just made it so that the edge button functionality works. I have included a patch for gconf to display AnyButton if it is set to 0. There is also a patch to make the edge size configurable because 1 pixel was too small and the mouse keeps slipping off when using it for the

I've recently drafted a rough idea of a composite manager agnostic protocol for leveraging the compositor for retained drawing in a way suitable for highly interactive and flexible applications. It seems to be that for anything like this to be a success it would have to be developed with the support of multiple window managers, and I would appreciate any feedback, ideas, and contributions to

Dennis Kasprzyk and I have been discussing some changes to how options are initialized. Problems with how options are currently initialized. 1. Helper functions are not used to initialize options, which means that if we make a change to the option structure, all option initialization code needs to be updated. Using helper functions will also reduces the amount of duplicate code. 2. No

Attached are my draft patches to add edge + mouse button to the actions It is useful because the edge bindings are too easily triggered, an edge + mouse button is good because it confirms the action. An additional side benefit is that the mouse wheel can be used for rotating the cube and for the switcher (it is an excellent alternative to alt-tab). I wanted to share the patches before cleaning

I've documented the 80+ functions available in compiz-scheme (those not available in regular scheme) at: http://people.freedesktop.org/~racarr/DOCUMENTATION and furthermore in the git repo. Additionally a 5 minute tutorial to scheme and a 5 minute tutorial to using compiz-scheme as a state replacement (though this is certainly not all it does!) is available at:

Hi, I'm working on a frontend for R. I have R running in a separate thread in my application using Rf_initEmbeddedR, and I'm using R_tryEval to run commands in R (i.e. I don't run the mainloop). Everything works fine, except the x11-device: I can open x11-windows and paint to them alright from R. However, the x11-window does not respond to any events. E.g. clicking the

Author: robert.moran Date: Sun May 31 11:13:23 2009 New Revision: 11 Modified: trunk/source/mxn.core.js trunk/source/mxn.js trunk/source/mxn.yahoo.core.js trunk/tests/index.htm Log: Added functionality to automatically load scripts needed. Allowed mapstraction default constructor to have provider omitted (will use first loaded provider). Minor change to yahoo implementation -

Where are we going? It's time to start thinking ahead and really figure out how to make Compiz survive, specially in lieu of Dennis' suggestion. The reality is that there has been the equivalent of no progress since the merge. We've basically only been in maintenance mode. The reason for this, from my point of view, is a complete lack of direction and leadership. We've

Here is a switcher patch to disable window list: It's very useful if you set opacity to 0. Then, window just bring to front one by one while switching. It's much more usable, i think, that small miniatures in a list where you don't see anything. While making this patch, a question come into my head, nobody know on compiz.biz and some people are as curious as me. Two code example:

Hi, there are two problems in devX11.c. The one is an undocumented nuisance and the other isn't a bug until you try to embed an X11 device in another window (think tktoplevel() in tcltk package...). Let's take a look at locator() first: Assuming you call locator() with a current X11 device, this call is handled in X11_Locator (src/unix/X11/devX11.c). When you have one window open and

I have been running Agent3.3 uner Linux debian sarge, wine 0.0.20050310-1.2, fake windows partition. Absolutely no problems, even when tackling large groups like binaries or advocacy. But the upgrade to V4 did not go well. I went back to 3.3 and managed to reproduce under reduced conditions: * Created a new, vanilla user called gorby * Created a new fake windows setup with a vanilla

Has anyone encountered this error or know how to correct it? I couldn''t find any Rails-specific info about this on google. Here are the circumstances: /usr/local/bin/ruby --version ruby 1.8.4 (2005-12-24) [i686-linux] /usr/local/bin/rails --version Rails 1.1.6 ## Create mcd app rails mcd -d oracle cd mcd ## Create oracle tablespace & user sqlplus ''/ as

I've put a scheme plugin in users/racarr/compiz-scheme on gitweb.open-compositing.org. Essentially it allows the user to define a startup file (~/.compiz/startup.scm) and fill it with scheme code to do neat things and extend Beryl. On one hand it acts like a super powered state plugin, on the other it lets you define useful behavior specific to what you do with your Compiz and share these

Beyond the general work on compiz-scheme (new wrappings, hooks, code improvements, etc), I've added a few large new things: 1. Key bindings with modifiers. This lets you from any of your scheme files/interactive prompt bind an arbitrary key + modifier to an arbitrary scheme function. So you can define new Compiz behaviors and shortcuts on the fly. 2. An interactive prompt. This sets up a

Our previous attempts to select a project name for CompComm have not gone well. We tried a poll but the names in the poll were not pre-qualified to determine if they were usable and the ?winning? name was also a strongly disliked name. Kristian and I each proposed a plan to select a name, but that effort got sidetracked by a massive flame war on the mailing list. While our community has some

I had always assumed that an action option should return true if it handles the action, but it seems like most button bindings actually return false which causes a few problems. 1. The clicks pass through to windows which is not good for rotate, screenshot or annotate. 2. I am trying to add a generic action notification which plugins can wrap to see when other actions are initiated and

I was always annoyed that you couldn't terminate an action with dbus so I have written this patch which fixes that. Hopefully this can be included. I wrote the patch trying to repeat as little code as possible so I just added a boolean parameter to the dbusHandleActivateMessage and changed the name to dbusHandleActivateDeactivateMessage. You could probably change the deactivate parameter