similar to: Blurring behind windows

I now use blur plugin thanx to window matching feature, thanx David ;) I have some bugs: http://hibbert.univ-lille3.fr/~cbellegarde/blur_4xbilinear_bug.png Here, i have some artefacts bugs with 4xbilinear. This blur mode is fast! May be a Nvidia drivers bug... http://hibbert.univ-lille3.fr/%7Ecbellegarde/blur_gaussian_fast.png Here, an amarok big window with just desktop, moving window is

I am having a few problems with blur which I notice other people are having too. Focus blur works perfectly (although only with 4xBilinear) When I start blurdemo, that works too. The problem is that sometimes changing the filter type crashes compiz. If I run it under a debugger it starts working again. All the filter types work with blurdemo. Blurset also works in that it sets the hint on

For some reason all mozilla and open office menus are Normal type. This causes problems with all plugins which use the window type. This patch is applied to all plugins and seems to work flawlessly. I am submitting it for blur because the first window of all firefox menus are blurred. I know its a hack, but at least it should be fairly harmless inside each plugin. It is always marked with

I forgot to give everyone an update on this. The blur plugin is in a reasonable state now. It requires an OpenGL implementation with an accelerated CopyTexSubImage2D path for usable performance and that's likely not going to change sometime soon. One major performance improvement can still be made, which allow us to avoid the CopyTexSubImage2D path whenever the area behind a blurred region is

Changes since 0.2.2: * Core Some stencil buffer requirements have been removed. Focus stealing prevention. Fragment attribute interface that allow plugins to perform more advanced fragment shading effects while integrating properly with other plugins. Use composite overlay window for output by default. Add file notification API.

There's now an extensible window matching interface in head. Initial commit message: Add extensible match interface. Match objects can be used for window matching but other objects than windows will likely be supported sometime soon. A match object contains a boolean tree of expressions and each expression can be implemented by a different plugin. The core interface only

Here are a few plugins I wrote. The put plugins gives you bindings to move windows around. I set it up so the numeric keypad is like the area of the screen. So <Super>KP_Home will move the window to the top left, etc ... It also does viewport moves which is handy when used with the plane plugin. I like the plane plugin in a 3x3 matrix matching the keypad, so with the keypad and some

Greetings everybody! For anybody working on blur-related things, take a look at this glitch I encountered: https://bugs.freedesktop.org/show_bug.cgi?id=10275 Best regards... Mirco "MacSlow" M?ller -- email - macslow@bangang.de www - http://macslow.thepimp.net lowfat - http://macslow.thepimp.net/sponsor-it

We've previously discussed if we should add some sort of selection option type and not use string options and string restrictions for that purpose. I don't think we need a new option type for this. The integer type should do just fine. The attached patch changes the blur plugin's filter option from string to integer type and adds the relevant metadata. I suggest that we change all

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

Attached is a quick patch which adds a logging framework to compiz. I think it should be fairly self explanitory. I think it should allow plugin writers to extend it for any purpose, but I would appreciate any feedback or comments before going any further. Regards Mike -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: logging.diff Url:

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

I have downloaded compiz-0.2.0 and tried to compile it. The INSTALL file talks about autgen.sh, but I am unable to locate it. I tried ./configure but it complains about a number of missing packages. Is there any docs on how to compile compiz on SLED 10 ? I have searched in a lot of places, but have not been able to dig up anything. A detailed list of what packages is required (and where to locate

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

The blur plugin has GL_ARB_fragment_program extension as a prerequisite. At least that's what I'm getting by looking at screen.c. I think there should be a check for the "CompScreen::fragmentProgram" flag somewhere in blur.c to prevent it from loading or at least executing a <null> pointer. I get a crash in line blur.c:1858, because CompScreen::programEnvParameter4f

I'm using compiz compiled for feisty by trevino, on a mobility radeon x1600 using fglrx 8.38.6 over Xgl 7.2.0. I'm experiencing some problems with the blur: after a short time using compiz the blur over the windows (most noticeably the terminal) becomes a opaque gray. I really don't know how to debug this problem... :( I'll be happy to give any information you'll need

Hi, On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl <kristian at bohemians.org> wrote: > > Feature-wise, Compiz 0.9.12.0 actually has fewer features as I understand it. With the move to OpenGL ES, several plugins got dropped. I understand some of that has been remedied, but 0.9 still does not come out ahead if my understanding is correct. I have asked around and this is what

Hi It seem that the fragment interface on certain plugins exceeds the amount of fragment operations possible on Intel GMA cards. This only occurs with the "water" and "blur" plugins. the plugins activate OK and do not report a missing GL_ARB_fragment_program in the server extensions. Waves appear when I use the water plugin with <Super><Ctrl> but there is no

Hi, some of you might noticed that there was recently some discussion on the Beryl ML about an interface which provides sharing functions and allows us to do library plugins. One example for this kind of plugins is text, which was recently ported to that system. I now want to explain here how it works in general. Core does save the shared library functions in a CompLibraryFunction struct: struct

This was a private mail and not supposed to go to the compiz list. Please don't don't read it unless you're on the compiz admin list. :) I've apologized to Jeff, Mike, Rico and Arturo for making this mistake and I'd like to apologize to anyone else who might have been offended by it. I guess the good part is that you get an uncensored view of what we feel about the community