Hi,
I don't agree with this conclusion, though: Releasing KWD with KDE just
moves the code-is-broken-due-to-unsynced-release problem from 'KWD is
broken when KDE code is changed' to 'KWD is broken when Compiz code is
changed'. I'm not sure how that improves things, especially given that
Compiz 0
Hi,
Let me first describe the current situation and the problems with it: Compiz
and KDE releases are out of sync. We are currently more and more integrating
features from the desktop shell into the window manager. In difference to
other desktop shells (GNOME Shell, Unity) Plasma still allows to
Am Mittwoch, den 19.05.2010, 10:05 +0200 schrieb Christian Mertes:
> On Mi, 2010-05-19 at 08:42 +0200, Danny Baumann wrote:
> > In the past (compiz
> > > 0.5.6 - 0.8.2) there may have been one or two that would stick on
> > > some weird XGL
> > > issue, bu
Hi,
> Dominique, you wanted the feedback, and List, I need your help. I have
> installed and fully configured (kicked the tires) on compiz 8.6 on openSuSE
> 11.0
> and on balance it is great. There are a few weird things going on. Most
> notably,
> the number of options in ccsm that now uncheck
Hi,
> how can I enable a plugin from the command line?
>
> I know how to *activate* it from dbus, i.e. do the equivalent of
> pressing "Ctrl-F9" or whatever the hotkey is.
>
> But I don't know how to *enable* it, i.e. do the equivalent of clicking
> the "enabled" checkbox in compizconfig setti
Hi,
> 1) When an application requests a topology change via
>_NET_WM_FULLSCREEN_MONITORS, Compiz does honor the topology
> change, but it
>does not refresh any monitor that has changed since the
> last
>_NET_WM_FULLSCREEN_MONITORS topolog
Hi,
> > This patch:
> > -> Changes the XRectangle definition to CompRect as part of the new
> > (unofficial) standard
> > -> Adds a getter for priv->iconGeometry and priv->iconGeometrySet
> >
> > The patch is attached.
> >
> > Kind Regards,
> >
> > Sam
> >
> > --
> > Sam Spilsbury
> >
>
> Hi,
>
Hi,
> >> Personally, I'd like to see x1/y1/x2/y2 instead of
> >> left/top/right/bottom. The reason is that while left etc. is the
> >> somewhat clearer term, x1 etc. is the more commonly used term for
> >> defining rectangles.
> >
> > Oh, and what I forgot: Wouldn't it be a good idea to derive
> >
Hi,
> > > Me and Dennis Kasprzyk changed CompRect to be more intuitive
> > and easily
> > > replace XRectangle use.
> > >
> > > This patch changes CompRect and whole Core.
> > >
> > > Thanks for attention.
>
> Personally, I'd like to see x1/
Hi,
> > Me and Dennis Kasprzyk changed CompRect to be more intuitive
> and easily
> > replace XRectangle use.
> >
> > This patch changes CompRect and whole Core.
> >
> > Thanks for attention.
Personally, I'd like to see x1/y1/x2/y2 instead
Hi,
> The problem appears to be that compiz is getting screen 0 geometry for
> screen 1, and as screen 0 is 800 pixels high and screen 1 is 1024 pixels
> high, screen 1 ends up with a black band across the lower section of the
> monitor that appears to be 224 (1024-800) pixels high.
>
> The issue
l10n updates
l10n updates
l10n updates
l10n updates
l10n updates
Christopher Williams (1):
Fix compatibility with newer libmetacity-private versions.
GtkStyle is colormap specific, so we can't use a new colormap each time
we create a pixmap.
Danny Baumann (11
Hi,
> > Hence I propose doing the following:
> >
> > - Add a "commands" plugin
> > Handling of arbitrary command bindings should be moved from core to this
> > plugin. Also, button and edge bindings for arbitrary commands as
> > requested by a number of people can easily be added to such a plugin
Hi,
currently, we have a bunch of stuff in compiz core that is entirely
Gnome specific, though it's designed to be general. What I mean is
- arbitrary command bindings
- terminal and screenshot command bindings
- "main menu" and "run dialog" toolkit actions
Neither of those is handled by the wind
Hi,
> > I think this is something we really need to fix as a community. Dennis
> > should have just been able to post a mail to the list saying 'Core is
> > broken, I have time to work on it, here is a list of features I
> > propose', have minimal discussion, have him present to us a prototype
>
Hi,
> You confused me... The spec goes top/bottom/left/right... Let me redo
> this that way...
>
> (monitor set: top/bottom/left/right - old code - new code)
> monitor #0 being 1280x800
> monitor #1 being 1280x1024
>
> A) - 1280x800+0+0 - 1280x800+0+0
> B) - 1280x1024+1280+0 - 128
Hi,
> - There's one reported regression: URL I will try to see what's
> happening there (and if I can reproduce it at all), but if you have any
> pointers, let me know.
Sorry folks, URL should read
http://forum.compiz-fusion.org/showthread.php?t=10642
I should better fill in URLs right away inst
ust pulled out a git clone of
> compiz and was getting ready to start looking at patching
> _NET_WM_FULLSCREEN_MONITORS into Compiz and I discovered that Danny
> Baumann had done just that literally the day before. WOOT! Thank you
> Danny!!!
You're welcome :)
> I spent some
Hi,
> I got a segmentation fault in compiz and after some analysis have a
> question about synchronization in core compiz functions.
>
> From time to time when I switch my laptop between users I see
> corrupted picture on the display. Also I see the following lines in
> logs:
>
> Dec 22 22:05:34
Hi,
> Nothing has worked with the compiz that includes nomad. I don't understand
> what
> nomad is other than a few brief descriptions of it enabling features for rdp
> on
> linux -- but the down side is it *kills* emerald. Foolish trade-off in my
> view.
Nomad is not on master, but on a separ
Hi,
> After reading the comments on:
> http://bugs.opencompositing.org/show_bug.cgi?id=379
>
> The problem stemmed from the inability to unload the gconf plugin via
> gconf. However, what would the alternative be?
>
> It seems like a better solution overall to simply treat conf plugins for
> w
Hi,
> Fedora 10 ships with compiz and launches it as: compiz
> --ignore-desktop-hints glib gconf
>
> This causes compiz to load the glib and gconf plugins at startup. This
> works fine.
>
> The problem arises when the gconf database does not include those
> plugins in /apps/compiz/general/all
/archive/individual/app/compiz-0.7.8.tar.gz.sha1
> > 7b8a67b5d5b4aa6a33fcf60691bfae757768ffa3 compiz-0.7.8.tar.gz
> >
> >
> > http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz.sha1.asc
> > (signed by Danny Baumann)
>
> Sorry folks, but I made a mis
compiz-0.7.8.tar.gz.sha1
> 7b8a67b5d5b4aa6a33fcf60691bfae757768ffa3 compiz-0.7.8.tar.gz
>
>
> http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz.sha1.asc
> (signed by Danny Baumann)
Sorry folks, but I made a mistake when creating the tarball which leads
to the KDE parts not building when
-0.7.8.tar.gz
http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.8.tar.gz.sha1.asc
(signed by Danny Baumann)
Additionally, a git clone of the source tree:
git clone git://git.freedesktop.org/git/xorg/app/compiz
will include a signed compiz-0.7.8 tag which points
Hi,
> For the past 1 or 2 compiz releases, for some reason it opens
> Yast software
> management full-screen with no window decorations in kde.
> kwin gives the normal windowed yast s/w management.
Does playing around with the "legacy fullscreen support" option in the
workarounds plugin ch
Hi,
Accidentially sent private only, forwarding to mailing list as well.
Regards,
Danny
> -Ursprüngliche Nachricht-
> Von: Danny Baumann [mailto:[EMAIL PROTECTED]
> Gesendet: Samstag, 28. Juni 2008 14:13
> An: 'Esben Stien'
> Betreff: AW: [compiz] Miss
Hi,
> > I strongly dislike supporting subwindow ID/profile tuples.
> The task of
> > window and compositing managers is and always has been to
> manage and
> > draw _toplevel_ windows, not subwindows. I don't really think that
> > adding a subwindow management infrastructure to compositing
Hi,
> Am 30.05.08, 14:32 +0200 schrieb Rémi Cardona:
> > Tomas Carnecky a écrit :
> > > Dennis Kasprzyk (compiz developer) wasn't happy that I want to
> > > attach properties to subwindows, instead he suggested to attach a
> > > list to the top-level window containing tuples of
> [(sub)window
Hi,
> I was looking into the source code in more detail and debuged the DBUs
> interface a bit and it seems to me that only a few commands of the
> compiz plugin are still "exported" as "actions" in version 0.7.6 of
> compiz.
>
> If I grep the source tree of compiz I find only 7 occurrences if
>
Hi,
> Thanks for a great compiz-0.7.6. The cylinder takes a little warming up
> to,
> but is really cool. Of all the boxes I have updated, I have one that now
> experiences the White Screen of Death (WSOD) when compiz is started. Killing
> X
> with ctrl+alt+backspace or ssh from remote
Hi,
> This isn't a cross post.
It's even worse: It's a repost without reference to your original
discussion (which is located at
http://lists.opensuse.org/opensuse/2008-05/msg00519.html).
> Wobbly windows seems to have changed in the last release and for the
> worse. On
> narrow windows,
Hi,
> Since upgrading to compiz 0.7, it does not start anymore on my x86_64
> system, with the error message
> compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going
> to work.
> compiz (core) - Error: Failed to manage screen: 0
> compiz (core) - Fatal: No manageable screens f
Hi,
> With the update to compiz 0.7.0-5.1, compiz-emerald and emerald-themes
> completely stopped working. Compiz will start and you can choose kde
> window decorations, but I cannot get emerald to work not matter what.
> Not from fusion icon, not from the cli with "emerald --replace &". It is
Hi,
> For those of us "out of the loop" a bit of late, does anyone have the
> following snippets of info:
>
> 1. Is this meant to be a dev release (e.g. odd number == dev)?
Yes. It should be a pretty stable dev release, though ;-)
> 2. What is the state of the fusion plugin set? Grab from git o
Hi,
> > Well, it's not so much a 'weird configuration' as a faithful
> > representation of reality. :) What to do with this information is policy
> > and thus not up to the X server.
>
> This should be obvious... The xinerama query is returning the actual
> heads, as it is supposed to. There are
Hi,
> > > "metacity doesn't know what is the full screen resolution"
> > > https://bugzilla.redhat.com/show_bug.cgi?id=431302
> > >
> > > Can you please look at it and say if this looks like a compiz, X,
> > > gnome which bug :)
> >
> > I've been aware of this issue for about a year or more now, b
Hi,
> I've been aware of this issue for about a year or more now,
> but never really considered it a bug. Like Danny sais in the
> cf bug report [1], it's totally wm-dependant how to treat this issue.
>
> However, I believe it makes sense for Compiz to have an
> option to ignore outputs that
Hi,
> Maybe the following description would help a bit to find a reason ?
> I have similar example. It wasn't always like this, it started in the past
> after one of upgrades of compiz (months ago, I think shortly after
> beryl-compiz merge). It may be also due to upgrade of Xorg (from 1.2 to 1.
Hi,
> > Hi, u found this bug with compiz turned on:
> >
> > "metacity doesn't know what is the full screen resolution"
> > https://bugzilla.redhat.com/show_bug.cgi?id=431302
> >
> > Can you please look at it and say if this looks like a compiz, X,
> > gnome which bug :)
> >
> > Thank you very much
Hi,
> > > > > > Hi,
> > > > > > I first would thank all of you for great work that you do compiz, it
> > > > > > really is one of poster child projects for opensource model of
> > > > > > developing great apps.
> > > > > >
> > > > > > I have one small bug[1] but it is irritaing me a lot :) so can
Hi,
> The ini plugin segfaults on startup. The following patch fixes it. Not
> sure why this hasn't been caught before - i guess not many people use
> the ini plugin.
That, and the error depends on memory initialization.
But in any case, you're correct; I've commited your patch.
Regards,
Danny
Hi,
> > > > Hi,
> > > > I first would thank all of you for great work that you do compiz, it
> > > > really is one of poster child projects for opensource model of
> > > > developing great apps.
> > > >
> > > > I have one small bug[1] but it is irritaing me a lot :) so can you
> > > > please look
Hi,
> Looking through the compiz.ini, I don't understand the
> option format.
> Example:
>
> as_run_command0 = F2,Button0,,0,false
>
> What are the fields? I get F2, but what is Button0
> (none?). What are the rest of the fields?
>
> as_run_command0 = Keys,MouseButton, ? , ? ,(t
Hi,
> SVG loading in Compiz was broken for some time on my system, giving
> errors like this when attempted:
>
> (process:32161): GLib-GObject-CRITICAL **:
> /build/buildd/glib2.0-2.14.1/gobject/gtype.c:2242: initialization
> assertion failed, use IA__g_type_init() prior to this function
>
> Thi
Hi,
> 2. Apparent program errors
> The software "kde-window-decorator" crashed yesterday after a bit of looking
> around.
> I guess that the same issue was reported by "tribunal" already.
> http://forum.compiz-fusion.org/showthread.php?t=5584
This problem is already fixed in both git head and 0.
Hi,
> > I've currently commited a fix for the window menu translation to master and
> > the compiz-0.6 branch.
>
> That is interesting.
>
> I have noticed that some actions are offered twice in the context menu of my
> GNOME GUI after Compiz Fusion was started.
> Example:
> English "Move to Anot
Hi,
> > I have such a plugin (dumping debug output to a file, including
> > timestamps, filenames automatically generated from PID and time/date)
> > lying around for some time. I meant to publish it sometime ago, but
> > forgot about it. I will do so this week.
>
> OK, thanks. Does it catch logM
Hi,
please do not top quote.
> Yeah, I was thinking of that, however it would be nice if I didn't
> have to add a dependency :-/
I have such a plugin (dumping debug output to a file, including
timestamps, filenames automatically generated from PID and time/date)
lying around for some time. I mea
Hi,
> I was until a couple of days ago joyfully running the latest git version
> of compiz. Today when I started it using a "compiz-manager" script
> (after updating to the most recent) I got the following error:
>
> /usr/bin/compiz (core) - Error: no 'core' plugin with ABI version
> '20071017' l
Hi,
> Is there a setting that would cause windows to open with their title
> bar hidden behind the GNOME panel? With Compiz disabled they always
> open below the panel (as if the bottom of the panel was the top of the
> screen).
>
> The windows still "snaps" to the panel when moved, so the windo
Hi,
> >> Gitweb seems tob e out of order for 0.6, but commit
> >> f6c2f52156aaaf5bc3fc4718de85e1befc92dca1 in the 0.6.0 branch for
> >> plugins-main should be what you're looking for.
> >>
> >>
> > thx!
> > will build a new f8 package ASAP.
>
> From the id I think Danny is referring to this:
> ht
Hi,
> > There is a bug report for this here:
> > http://bugs.opencompositing.org/show_bug.cgi?id=431
> >
> > It seems to be fixed for Firefox in the current git version.
> >
> I cannot find any fix for this in git the commit linked above is
> already
> part of the 0.6.0 release.
> I heard that the
Hi,
> In Ubuntu 7.10 with KDE, I have compiz running under XGL. Although
> Beryl ran fine in Ubuntu 7.04, Compiz will not enable 3D effects such
> as wobbly windows. Other effects, such as minimize/restore animations,
> work properly. The machine is a Dell Inspiron 6400 / E1505 laptop,
> 2Ghz Inte
Hi,
> This release has still the "flipping window" problem I described a while back
> (mail from 25.8.)
>
> When moving a window fast to the left screen, so the cube spins, the window
> seems to "jump" to the other side of the screen and flip back.
Yes, I know, wobbly snap still has issues. I
-0.6.2.tar.gz
http://xorg.freedesktop.org/archive/individual/app/compiz-0.6.2.tar.gz.sha1.asc
(signed by Danny Baumann)
Additionally, a git clone of the source tree:
git clone git://git.freedesktop.org/git/xorg/app/compiz
will include a signed compiz-0.6.2 tag which points to
Hi,
> It's not perfect, assumes s->numScreens < 10 and that DISPLAY ends with
> '.?', but it works and I can start apps on the second screen.
I've commited an enhanced version of your patch which should work with
every display string thrown at it. I've also commited your other patch
to the decora
Hi,
> > A new compiz release 0.6.0 is now available from:
>
> Are you aware that the compiz.org website is still lagging behind? It
> still mentions 0.4.0 as the current stable
Yes, I am, but unfortunately I have no access to the site.
Rico, can you please update the site accordingly (and p
Hi,
> > I will release a 0.6.2 ASAP that fixes that problem, but until then,
> > please either apply this commit to the release tarball:
> > http://gitweb.freedesktop.org/?p=xorg/app/compiz.git;a=commit;h=b6c6acc70261d0942977441914c23e7a1c99215e
> > or continue to use the compiz-0.6 branch.
>
> H
Hi,
> > Unfortunately I noticed today that release 0.6.0 contains a bad problem
> > that allows e.g. desktop windows being stacked over normal windows when
> > they are mapped. This results in normal windows and/or panels not being
> > visible when compiz is launched with the Gnome or KDE sess
Am Dienstag, den 02.10.2007, 11:45 +0200 schrieb Jesper Andersen:
> Hi.
>
> I was not able to find any notice of this issue in either the forums or
> bugzilla (http://bugs.opencompositing.org/) (is that still used btw) so
> I am posting it here in the hope that it is useful to someone.
>
> I am u
Hi,
> Additionally, a git clone of the source tree:
>
> git clone git://git.freedesktop.org/git/xorg/app/compiz
>
> will include a signed compiz-0.6.0 tag which points to a commit
> named:
> 6218259ff6ec71a1eb6e9062646d63794947747e
>
> which can be verified with:
>
Hi,
> I think you should look at extrawm compiz-fusion plugin if you want to
> add such features...
>
> > Did a pretty simple patch to allow raising/lowering window using key
> > bindings, which I personally use a lot in other window managers.
> >
> > As simple as it is, it changes the
Hi,
> >> Is there a setting for that somewhere? In a previous incarnation, I
> >> was using the gconf backend for compiz-fusion, but it was corrupting
> >> the settings. My current installation doesn't seem to allow the gconf
> >> backend as an option (at least, it doesn't appear in the menu).
>
Hi,
> > Kristian, is there any specific reason that your fixes are not in
> > master, but only in the 0.6 branch? It looks to me as it would make
> > sense to include them in master as well.
>
> I'm pretty sure I put them on master (the default-plugins patch needed
> some adjusting) and I see the
Hi,
> > > Since I have some interest in seeing the 0.6 release go out, I can
> > > volunteer to drive that unless somebody else wants to.
> >
> > I started charry-picking to the 0.6 branch, but if you have some spare
> > time, help is always appreciated ;-)
> > I will pick up the plain bug fixes f
Hi,
> > I'm not sure what will end up in 0.6 and not. I'm not going to be much
> > in charge of what goes into 0.6 and not. We can revert the commit that
> > added the XCB requirement and re-base the 0.6 branch on head if people
> > are interested in that.
>
> I think 0.6 got branched at a good t
Hi,
> > > > You are right. This also works as intended. I walked a false path
> > > > there, sorry.
> > > > The real problem is that we don't select for FocusChange events for
> > > > frame windows and thus never get FocusIn events for them.
> > > > Correcting this revealed another problem: The
Hi,
> > >> today, I noticed a problem in focus handling for shaded windows which is
> > >> pretty easy to reproduce:
> > >>
> > >> - Disable "Click to focus"
> > >> - Shade a window
> > >> - Hover another window
> > >> - Hover back to the window frame of the shaded window
> > >> - Press Ctrl+Alt+
>> today, I noticed a problem in focus handling for shaded windows which is
>> pretty easy to reproduce:
>>
>> - Disable "Click to focus"
>> - Shade a window
>> - Hover another window
>> - Hover back to the window frame of the shaded window
>> - Press Ctrl+Alt+S
>>
>> Expected behaviour would be
Hi,
> ccs has taken a different approach and is afaik an abstraction layer on
> top of the configuration system provided by compiz core. It has its own
> backend interface that allows different storage systems to be used. It
> provides an API for which applications like ccsm can written without
>
Hi,
> On Sat, 2007-06-23 at 19:53 +0200, Bellegarde Cedric wrote:
> > In current git, when starting a resize and finish it without any
> change,
> > resizeTerminate() need to do a resizeDamageRectangle().
> >
> > This patch fix the issue...
>
> ok, should be fixed in head now.
It should be fixed
Hi,
> I've updated the screen edge trigger delay patch I posted on this list
> on 19/06/07.
>
> The prevention of edge delays for edge action that don't want to be
> delayed is now done more appropriately by a metadata tag
> () and the edge delay is now also applied to edge
> DnD actions.
>
> I
Hi,
> This small patch fixes the place where the "activate" event is sent in
> Scale to notify others about when its state goes back to normal.
> Previously it happened when its (going back to normal) animation
> starts, where it should have been when the animation ends. Without
> this fix, this a
Hi,
> With this mail I would like to make a proposal to add additional informations
> to the core and plugin metadata files. Currently these tags are already
> handled in the ccs configuration system. Ccs automatically adds this
> informations to the core/plugin option set, but I think that it
Hi,
I've updated the screen edge trigger delay patch I posted on this list
on 19/06/07.
The prevention of edge delays for edge action that don't want to be
delayed is now done more appropriately by a metadata tag
() and the edge delay is now also applied to edge
DnD actions.
I'm still open for
Hi,
> The patches I sent earlier apparently only worked for window closing.
> Animation's activate event was too late for suppressing minimize/open
> fading. Here are working patches that are also simpler, they don't
> involve any compiz-event handling. Now Fade just checks at the
> beginning whet
Hi,
> The minimize plugin conflicts with Animation. For example, it doesn't
> let Animation draw shade animations, and interferes with other window
> event animations. The animation plugin now minimizes the relevant
> effects to taskbar, so using the two plugins together doesn't make
> sense anymo
Hi,
> Currently some plugins call matrixScale with z parameter 0. This
> probably wasn't the intention and it might cause problems (it did in
> the past). 1 should be passed instead. This patch fixes this typo.
Yes, that definitely makes sense. I've just applied your patch.
Regards,
Danny
Hi,
>> In current git, placement mode option isn't working.
>>
>> This patch fix this issue.
>>
>> Cedric
>
> Hmm, i just miss to remove the old placeMode struct :(
I've just applied your patch - thank you.
Regards,
Danny
___
compiz mailing list
comp
Hi,
> > Currently, the cube plugin uses mipmapping only when cube is unfolded.
> > When the cube is rotated, mipmaps are not used, which leads to ugly look
> > of textures.
> >
> > The attached patch fixes this. This leads to another kind of artifacts,
> > which are fixable with anisotropic filter
Hi,
today, I noticed a problem in focus handling for shaded windows which is
pretty easy to reproduce:
- Disable "Click to focus"
- Shade a window
- Hover another window
- Hover back to the window frame of the shaded window
- Press Ctrl+Alt+S
Expected behaviour would be that the shaded window is
Hi,
I have created an addition to the regex plugin that allows case
insensitive matching for title/class/name/role. To enable the case
insentive matching, I chose to prepend an 'i' before the tag (ititle=,
iclass=, ...). The patch is obviously attached ;-)
Are there any objections against putting
Hi,
a popular feature in Beryl currently missing in Compiz was the ability
to delay triggering screen edge actions, so that you have to keep your
pointer at the screen edge for a while for the action to be triggered to
prevent accidential triggering.
The attached patch adds that feature. I'd like
Hi,
currently, all sorting order of the core and core plugin options inside
the metadata files is based on the order they are listed in the C source
files. Unfortunately, that's not optimal for automatic settings manager
GUI generation.
DO you think it's ok to sort them by functional groups? This
Hi,
> > Thanks for putting these changes in git, it indeed makes more sense
> > than the way I did it first.
> > I re-made the transparent cube patches to work now with this new interface.
> > Tell me what you think about it.
I re-did Roi's patches for latest cube plugin changes and coding style.
Hi,
> Why was the scale binding changed and not plane's and wall's then?
> ctrl + alt + up is a very good binding for scale.
What would be your suggestion for wall and plane then? cube uses Crtl
+Alt+Left/Right for viewport switching left/right, so in my opinion it
makes a lot of sense if wall an
Hi,
> isnt the default binding for scale ctrl + alt + up...? at least that's
> mine...
That was the case before (until today morning CEST), but it was changed
because it conflicted with the plane and wall plugins.
Regards,
Danny
___
compiz mailing li
Hi,
> gtk-window-decorator: Could not acquire decoration manager selection on
> screen 0 display ":0.0"
Which version of Compiz do you use? I just tried running
"gtk-window-decorator --replace &" on my box (F7 / latest Git Compiz)
and it worked just fine. Or do you by any chance already have som
Hi,
> > I finally have found the reason for the problem: It is wrapping into
> > initPluginFor(Display|Screen) while executing initPluginFor(Display|
> > Screen).
> > Let me show this with the call stack. 'storage' in this example is the
> > option storage plugin.
> >
> > - d->initPluginForDispla
Hi,
> > since quite some time I encounter a problem which I believe is in the
> > dbus plugin: Sometimes when I load or unload plugins by changing the
> > configuration, all settings of all plugins are reset. At the same time,
> > the following message appears multiple times in the terminal I star
Hi,
I just noticed that Compiz' window base size calculation in the function
recalcNormalHints() is broken. If both PMinSize and PBaseSize are set,
the base size is overwritten by the minimum size first and after that
the minimum size is overwritten by the base size again. This leads to
the base s
Hi,
since quite some time I encounter a problem which I believe is in the
dbus plugin: Sometimes when I load or unload plugins by changing the
configuration, all settings of all plugins are reset. At the same time,
the following message appears multiple times in the terminal I started
Compiz from
Hi,
> Plugin dependencies have not yet been moved to the meta data system. I'd
> like some feedback before we do this. I suggest that we use tags similar
> to this:
>
>
>
> large-desktop
>
>
> png
> some-feature
>
Hi,
> I think there's a naming error in the current git metadata:
> metadata/compiz.schemas and metadata/compiz.xml should be named
> metadata/core.schemas and metadata/core.xml.
>
> In my installation all my core settings are ignored: renaming the file
> /usr/share/compiz.xml in /usr/share/core.
Hi,
> is anybody already working on porting the extra plugins (those ported
> over from beryl) to compiz 0.5.0? I'm especially thinking about the
> animation plugin. Or is this something to be addressed post-unification?
For the sake of completeness and if you once want to work with the Git
versi
Hi,
> I am fairly sure that this is just a bug in the codes logic, but
> I thought I should check first
>
> I noticed that the function was always returning true if only
> one grab is checked for (maybe other cases too)
>
> If nobody shouts I shall commit it because the behaviour in
> my plugin
Hi,
> > please find attached a patch that makes the behaviour of window
> > activation when a window is closed optional.
> > Currently, always the last active window is activated. Sometimes this
> > might not be the desired behaviour, but users (like me ;-) ) would like
> > the window under the po
Hi,
please find attached a patch that makes the behaviour of window
activation when a window is closed optional.
Currently, always the last active window is activated. Sometimes this
might not be the desired behaviour, but users (like me ;-) ) would like
the window under the pointer to be activate
Hi,
> I intend to make compiz depend on XCB and Xlib/XCB sometime soon so we
> can start using XCB where it's beneficial [1]. I'm mostly interested in
> using it for asynchronous reading of window properties but we should
> eventually try to use it for as much as possible. Removing Xlib
> complete
1 - 100 of 147 matches
Mail list logo
