similar to: window matching interface and the new match option

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

It is a common request and I think it can be useful. The problem with beryl blur is that it is way too slow. I haven't poured through all of their code but I strongly suspect that there is some intensive code to work out where to blur. I would be happy with just a basic blur under transparent windows. Is there anything that can be done in the core to make effects underneath transparent

Hi, I just compiled and installed the latest compiz from git head and I have a strange issue with windows positioning: all newly created windows are placed at 0,0 (upper left corner) of the screen, so the title bar (and menu bar too) is under my gnome panel. I attach a screenshot to show the problem. I can't understand if this is a problem of compiz configuration (plugin order or something

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

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 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

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

It seems to me that the plugin dependencies are not flexible enough for most plugins. The particular problem I am thinking about is animation/group and fade. They both specify RuleAfter but compiz interprets that as 'load after AND require it', there is a Require rule, but this relates to features not plugins. I would like to propose these changes and definitions, they seem more logical

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

Listmates, I installed 8.2 on opensuse 10.3 from the opensuse XGL repository to replace 7.6. Compiz works with the nvidia 8600 GT card (512M of GDDR3) on the box, but the ctrl+alt <- -> switching behavior is really bad. In 7.6, the ctrl+alt <- -> desktop switching changed desktops crisply with just the slightest hint of the cube detected during the very short and nice switch.

Hello. System info: OS: FC6 x86_64 video: Nvidia GF 7900 GT, driver version 97.55 compiz version: git config backend used: ccp I can reproduce this crash every time on my system. When blur plugin is active and I try to access any right-click menu, regular application menu or drop-down list, compiz crashes. Backtrace produced by crashhandler plugin shows crash in blur.c in function

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

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, I've just updated compiz in fedora rawhide and wanted to post a quick overview of the patches we still carry. Patch details are available here: http://cvs.fedora.redhat.com/viewcvs/rpms/compiz/devel terminate-move.patch restart.patch These are already upstream, but not yet in a released version. aiglx-defaults.patch tfp-server-extension.patch These two paper over a problem in

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.

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

I know this list is meant for discussion of compiz specifically, but .... 1) I sometimes see compiz spit out "Could not bind pixmap to texture" messages, even though it _appears_ to be working fine. I randomly guess that this is due to me running out of video memory (iirc I have 64mb of vram). Is that possibly a problem? I think Vista and OS X manually manage video

This is a somewhat controversial subject which I only reluctantly bring up. I honestly believe that open discussion is the only way to run a project, and I apologize in advance if I offend anyone. I got what should have been an easy question on #compiz a few days ago. A user came in and asked "What version do you recommend I use?". I honestly didn't know what to say. >From a

I'm getting about 1 frame every 7 seconds with alpha or focus blur enabled. Is this normal? I get around 30-40 FPS when using water on high settings. Would framebuffer_object support for the driver be of any use? Would it make things faster? Thanks in advance Sam