similar to: Fragment interface on Intel

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

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

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

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

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

On Mon, Nov 17, 2014 at 11:11 AM, Sam Spilsbury <smspillaz at gmail.com> wrote: > > On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl > <kristian at bohemians.org> wrote: > > So to sum up: Equal stability, fewer features, but actively maintained. > > > > In the end I told the user in question that 0.9.12.0 is the latest > stable version, but 0.8.9 has

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

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

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)

Hi everyone If you''ve seen this ticket, http://dev.rubyonrails.org/ticket/4782, you''ve noticed I have tried to make scrollable autocompleter work. The scrollIntoView works great, however the iframefix for IE didnt work in the previous change. This is fixed now. Also the "blur-on-scrollbar-click" should not work in both IE and Safari (can someone confirm this?) It all

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

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

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.

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

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.

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 thought I''d seen some discussion on this, but can''t find it. I have a text area that I''d like to save on blur unless the user clicks cancel. Anyone got a nice example of this? It''s non-obvious to me how I force the submit via javascript. Thanks, pt. -- Parker Thompson http://www.parkert.com/ 510.541.0125