search for: pluginsetscreenoption

Hello! Currently, in plugins like "state", when having list options, you have to parse all windows on the screen and update their properties... I find this so ugly. In fact, pluginSetScreenOption() give a pointer on the first element of the list (CompOptionValue). You don't know what list element has changed ! I think it should be prettier to give a pointer on the first element of the list at plugin initialisation but give a pointer on the "just changed" element of the lis...

...w that MINIMIZED option had change if we do nothing more than returning TRUE. After looking the code, i saw this: ss->opt[SWITCH_SCREEN_OPTION_MINIMIZED].value.b So my question is: When do i have to directly read CompOption? When do i have to add a member to my plugin struct and update it in pluginSetScreenOption() ? Cedric -------------- next part -------------- A non-text attachment was scrubbed... Name: switcher.patch Type: text/x-diff Size: 6138 bytes Desc: not available Url : http://lists.freedesktop.org/archives/compiz/attachments/20061111/2d97a036/switcher.bin -------------- next part --------------...