Re: [compiz] Couldn't activate plugin 'rotate'
Dennis Kasprzyk wrote: Am Montag 16 Juli 2007 20:49:32 schrieb Kresimir Kukulj: First, I would like to compliment you all for a great work you put in developing compiz. I have it running for more that a month and it did not crash. Stability is very good. Great work! Today I updated compiz from git tree and found that rotate generates this error: compiz (core) - Error: Couldn't activate plugin 'rotate' The problem is that the load after cube got removed from the rotate metadata. I reverted it now. The ccs configuration system doesn't handle require rules automatically as load after rules. There is also a case where we have a require and a load before rule for the same plugin (3d). Thanks, that fixed it. -- Kresimir Kukulj ++ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] Couldn't activate plugin 'rotate'
First, I would like to compliment you all for a great work you put in developing compiz. I have it running for more that a month and it did not crash. Stability is very good. Great work! Today I updated compiz from git tree and found that rotate generates this error: compiz (core) - Error: Couldn't activate plugin 'rotate' Rotate does not function. Any ideas ? I run gconf backend. Browsing through compiz site I did not find any guidelines of what is needed to send a bug report. Or I missed it ? I hoped compiz has some verbose option that could shed some light on why rotate initialisation fails. I use --indirect-rendering to avoid nvidia black window bug (somehow it helps). compiz --sm-disable --indirect-rendering --replace ccp! Backend : gconf Integration : true Profile : default Adding plugin winrules (winrules) Adding plugin snow (snow) Adding plugin decoration (decoration) Adding plugin crashhandler (crashhandler) Adding plugin regex (regex) Adding plugin rotate (rotate) Adding plugin fade (fade) Adding plugin reflex (reflex) Adding plugin move (move) Adding plugin svg (svg) Adding plugin ring (ring) Adding plugin showdesktop (showdesktop) Adding plugin png (png) Adding plugin snap (snap) Adding plugin scale (scale) Adding plugin thumbnail (thumbnail) Adding plugin video (video) Adding plugin zoom (zoom) Adding plugin screenshot (screenshot) Adding plugin switcher (switcher) Adding plugin annotate (annotate) Adding plugin fs (fs) Adding plugin wobbly (wobbly) Adding plugin water (water) Adding plugin neg (neg) Adding plugin resize (resize) Adding plugin fakeargb (fakeargb) Adding plugin trailfocus (trailfocus) Adding plugin tile (tile) Adding plugin splash (splash) Adding plugin dbus (dbus) Adding plugin mblur (mblur) Adding plugin bench (bench) Adding plugin inotify (inotify) Adding plugin cubereflex (cubereflex) Adding plugin wall (wall) Adding plugin put (put) Adding plugin extrawm (extrawm) Adding plugin cube (cube) Adding plugin firepaint (firepaint) Adding plugin blur (blur) Adding plugin addhelper (addhelper) Adding plugin glib (glib) Adding plugin minimize (minimize) Adding plugin plane (plane) Adding plugin text (text) Adding plugin clone (clone) Adding plugin expo (expo) Adding plugin resizeinfo (resizeinfo) Adding plugin opacify (opacify) Adding plugin fadedesktop (fadedesktop) Adding plugin imgjpeg (imgjpeg) Adding plugin place (place) Adding core settings (General Options) Adding plugin group (group) Adding plugin animation (animation) Initializing core options...done Initializing winrules options...done Initializing decoration options...done compiz (core) - Error: Couldn't activate plugin 'rotate' Initializing move options...done Initializing zoom options...done Initializing wobbly options...done Initializing resize options...done Initializing put options...done Initializing resizeinfo options...done Initializing imgjpeg options...done Initializing place options...done Initializing fade options...done Initializing cube options...done Initializing expo options...done Initializing scale options...done Initializing switcher options...done Active Plugin List update -- Kresimir Kukulj [EMAIL PROTECTED] +--+ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] state plugin
Robert Carr wrote: The Compiz-scheme can function as a state plugin of sorts. It embeds the Guile interpreter for the Scheme language in to a Compiz plugin and provides bindings/hooks in to events. You can find it at http://gitweb.opencompositing.org (compcomm/plugins/compiz-scheme) it has an example startup file with commented snippets including state like usage and a few other documentation and tutorial files. As to porting the original state plugin, there isn't really any documentation on ... anything, though I think the winrules plugin (also at gitweb.opencompositing.org) does something similar. Thanks for the info. I just looked at compiz-scheme and it seems to be able to to what I want, but it may take me some time to figure scheme :) Looks really nice :) move-window window dx dy - Move window by dx and dy in the x and y coordinates respectively. move-window-to window pos-x pos-y - Move window window to pos-x and pos-y. No checking is done for viewport bounds. x,y are top left corner ? I may hardcode coordinates for each desktop. Is there a way to know how big desktop is and how many sides my cube plugin uses so I could divide that and get start coordinates of each viewport ? Also, is there a way to remove window decoration from a specific window ? Cant find it in you docs. On 5/17/07, Kresimir Kukulj [EMAIL PROTECTED] wrote: 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 old port can be found here: http://www.anykeysoftware.co.uk/compiz/plugins/state.tar.gz This is a bit old and does not use new plugin system for options (metadata). I am tyring to see if it could be tweaked to new plugin infrastructure, but it is not trivial (or at least not for me :)). Can someone point me to some documentation so I could port this. Or is this functionality already planned for compiz (or maybe someone already has functonal plugin?). Regards Kresimir -- Kresimir Kukulj [EMAIL PROTECTED] +--+ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz -- Kresimir Kukulj [EMAIL PROTECTED] +--+ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] state plugin
Mike Dransfield wrote: Kresimir Kukulj wrote: Robert Carr wrote: The Compiz-scheme can function as a state plugin of sorts. It embeds the Guile interpreter for the Scheme language in to a Compiz plugin and provides bindings/hooks in to events. You can find it at http://gitweb.opencompositing.org (compcomm/plugins/compiz-scheme) it has an example startup file with commented snippets including state like usage and a few other documentation and tutorial files. As to porting the original state plugin, there isn't really any documentation on ... anything, though I think the winrules plugin (also at gitweb.opencompositing.org) does something similar. Thanks for the info. I just looked at compiz-scheme and it seems to be able to to what I want, but it may take me some time to figure scheme :) Looks really nice :) move-window window dx dy - Move window by dx and dy in the x and y coordinates respectively. move-window-to window pos-x pos-y - Move window window to pos-x and pos-y. No checking is done for viewport bounds. x,y are top left corner ? I may hardcode coordinates for each desktop. Is there a way to know how big desktop is and how many sides my cube plugin uses so I could divide that and get start coordinates of each viewport ? Also, is there a way to remove window decoration from a specific window ? Cant find it in you docs. This is already built into the decoration plugin. You can set the decoration/allscreens/decoration_match to any valid window match string. For example to not have borders on all firefox windows then you should set it to any !class=Firefox-bin For more information on window matching see here: http://forum.compiz.org/viewtopic.php?t=605 and here for the original announcement http://lists.freedesktop.org/archives/compiz/2007-February/001448.html Thanks! It does exactly what I want. Maybe this should be put to some docs section. On 5/17/07, Kresimir Kukulj [EMAIL PROTECTED] wrote: 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 old port can be found here: http://www.anykeysoftware.co.uk/compiz/plugins/state.tar.gz This is a bit old and does not use new plugin system for options (metadata). I am tyring to see if it could be tweaked to new plugin infrastructure, but it is not trivial (or at least not for me :)). Can someone point me to some documentation so I could port this. Or is this functionality already planned for compiz (or maybe someone already has functonal plugin?). Regards Kresimir -- Kresimir Kukulj [EMAIL PROTECTED] +--+ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz -- Kresimir Kukulj [EMAIL PROTECTED] +--+ Remember, if you break Debian, you get to keep both parts. ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] state plugin
Mike Dransfield wrote: Kresimir Kukulj wrote: Mike Dransfield wrote: Kresimir Kukulj wrote: 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 old port can be found here: http://www.anykeysoftware.co.uk/compiz/plugins/state.tar.gz I have updated this now and it should work with current git. This is a bit old and does not use new plugin system for options (metadata). I am tyring to see if it could be tweaked to new plugin infrastructure, but it is not trivial (or at least not for me :)). The whole state plugin is being replaced by the new advanced window matching as well as the winrules plugin. Winrules does not support viewports yet so I have updated this for you. This plugin will almost certainly be removed at some point. Thanks, I tried it but plugin has no properties (I ticked checkbox in ccs-settings). I see in tarball you have schema file but no xml. Is that problem ? I use ccp (ccs) as backend, not gconf. Is that my problem? Yes, and yes :) If you want to use ccs-settings then you will need to make an xml file with the options in it. What is the default/preffered backend ? ini, gconf or ccs ? Depends on who you ask ;) The default is gconf, preferred depends on requirements and taste. I personally prefer ini because its much easier to just edit a textfile than click click click (for me anyway). If you use ini or gconf then you will be able to set the options without the xml file. I saw on forum some howto and used ccp :) I will switch to gconf and try this plugin. If winrules will get viewport placement support soon (relatively), dont waste time fixing this old plugin (state) just for me. It was a hatchet job, I would not be too grateful ;) Uh, my english is a bit lacking. Miriam-webster: 'hachet job' = a forceful or malicious verbal attack Did not quite get that remark :( Viewport placement could probably be added to the place plugin and it would work well with the other placement modes. That would be nice. Also, nice feature of old beryl's plugin (window states) is so user can position windows (top-left, bootom-right ... etc) WHERE they should be on particular viewport. This together with viewport placement will provide that windows stay on correct desktops and desired location in viewport on restart. That would be great! Thanks for your effort. I think winrules does this, otherwise place would be the obvious plugin for it. I think there is no such functionality in winrules. And a small question, I use cube, and use keyboard shortcuts to directly switch to desired viewport. Cube is rotated and just when it is finished rotating it does little left/right setting movement. Can that be turned off ? I would like switching to be as fast as possible. Tried to accelerate settings but if switching from viewport 7 to 2 cube must rotate a longer distance and settling (small left/right oscillating) effect is very noticable. Try adjusting the timestep options, they generally affect the springyness of action movements. I think you need to make the value smaller. I did. And it makes it faster (springyness), but still can be seen. It is more noticable when cube must rotate couple od viewports to get to desired one. And finally, is there a way to avoid NVIDIA black bug ? I know that this is a driver problem (some out of memory condition in driver) but is there a workaround ? From old beryl forums this combination prevented black windows: Don't use COW Force AIXGL XGL binding XGL rendering That options are from beryl-manager (under advanced beryl options). Don't know why that combinations prevents black bug but it does. I did not see noticable performance drop using that combination of settings. Any suggestion would be welcome. Those options look like they just set the server that compiz is running on. The COW option is now gone. Do you use AIGLX? I have not heard of any workarounds for the black window bug. I found that information here: http://www.nvnews.net/vbulletin/showthread.php?t=84562page=10 Also I have: Option XAANoOffscreenPixmaps true Option RenderAccel true Option AddARGBGLXVisuals true Option DisableGLXRootClipping true On that forum they say that 'Don't Use Cow force AIGLX XGL binding XGL rendering' all must be used. And for me, that combination did the trick. No black window bug. Without that wierd combination of setting I had black windows very often :( It would be nice if NVidia would care about such bugs, and it suxx to make workarounds in an application just for them
