mike at blueroot.co.uk
Mon Oct 9 16:39:26 PDT 2006
> Initial position isn't working because of the name of the atom being
> sent to put. In state.c at line 913
> XInternAtom (w->screen->display->display, "_BERYL_PUT_WINDOW"
> should be XInternAtom (w->screen->display->display, "_COMPIZ_PUT_WINDOW"
> Also, if you didn't know, initial position uses put to do the actual
> window moving. So it needs to be loaded too.
I should have noticed this, I thought it would be something like this.
> This was another area where I was unsure of how to actually pull this
> off. It was never my intention to use put in this way, but it was
> requested by a lot of people so I did the best I could.
> As usual, any advice or suggestions are welcome.
I am no expert but I think that if you look at the dbus code you can see
that the dbus
plugin communicates with the plugin that is being activated through its
this (from dbusHandleActivateMessage).
There is some code in rotate.c which gets the option from the cube to
detect if it is
in or not.
p = findActivePlugin ("cube");
if (p && p->vTable->getScreenOptions)
CompOption *options, *option;
options = (*p->vTable->getScreenOptions) (s, &nOptions);
option = compFindOption (options, nOptions, "in", 0);
rs->invert = option->value.b ? -1 : 1;
This could be adapted to check for the put plugin and use that, if not
just revert to the
internal move functions.
>> *Water Quad Patch*
>> I also have a patch from moppsy for the quad water wave. It seems to
>> work, I removed
>> the shiver patches because they require patches to wobbly.
> Oh, this is such a hack. I tried to just follow the conventions in the
> source and extend line into quad. I'm not sure if I did softwareQuads
> correctly, It's just a data munge to squeeze it through softwareLines.
I am not expecting David to accept all of the patches that I have but
they are there if anyone
wants to play around with them.
More information about the compiz