gmane.comp.video.opengl.compiz.general

Window listing on different workspaces

Max Liebkies — 2011-07-21T11:57:29

Hello everyone,

what I am trying to achieve seems rather simple. I would like to
enumerate all open windows with respect to their current workspace. The
problem seems to be that Compiz does not differentiate between
workspaces as other (EWMH compliant?) window managers do. I'm not even
sure whether this is a bug or a design decision. Let me explain this
with an example:

Running Compiz gives me this:
$ wmctrl -l
0x02a00001  0         N/A N/A
0x02a00002  0         N/A launcher
0x01a00005  0 max-station Kontaktliste
[...]

But I think it should rather be like this:
$ wmctrl -l
0x02a00001  0         N/A N/A
0x02a00002  0         N/A launcher
0x01a00005  1 max-station Kontaktliste
[...]

So. Is there any way to achieve this? I need this to get a Python tiling
script working. Without the differentiation between workspaces all
windows will be tiled when using something similar to PyTyle, stiler,
etc.

I'm currently running Compiz 0.9.4.0 (unmodified) on Ubuntu 11.04 with
Unity.

Cheers and thanks in advance,

Max Liebkies

An Invitation to Neuroscientists and Physicists: Singapore Citizen Mr. Teo En Ming (Zhang Enming) Reports First Hand Account of Mind Intrusion and Mind Reading

Singapore Citizen Mr. Teo En Ming (Zhang Enming — 2011-05-17T12:38:23

16 May 2011 Monday 7:28 P.M. Singapore Time
For Immediate Release

SINGAPORE, SINGAPORE - Singapore Citizen Mr. Teo En Ming (Zhang Enming) 
would like to report first hand account of mind intrusion and mind 
reading. I have been hearing voices for quite some time now but I have 
not been able to identify the persons physically. A number of 
un-identified persons have intruded into my mind and they are able to 
read my thoughts. I could not explain the mechanism by which these 
un-identified persons have been reading my mind at the moment but there 
is definitely a scientific explanation for it. I know very clearly that 
I am not suffering from schizophrenia at all.

I am fully aware that no common man would believe me except the select 
few scientific researchers working in top secret government projects and 
the human guinea pigs who are being experimented on. One of the 
possibilities is that I have a microchip implanted into my brain, 
possibly when I was an infant. It may take a few years, a few decades, 
or even a few centuries before mind reading is finally brought to light 
before the general public.

I would like to invite neuroscientists, engineers and physicists to 
speak on the scientific explanation behind mind intrusion and mind reading.

Please remember what Singapore Citizen Mr. Teo En Ming (Zhang Enming) 
have said. Mark my words. You will know the truth in future. It is no 
longer a conspiracy theory. I can affirm that it (mind intrusion and 
mind reading) is indeed happening to me.


Yours truly,
Singapore Citizen Mr. Teo En Ming (Zhang Enming) 
Dip(Mechatronics)(Singapore Polytechnic) BEng(Hons)(Mechanical 
Engineering)(National University of Singapore)
Singapore Identity Card No/NRIC: S78*6*2*H
Toa Payoh Lorong 5, Singapore
Mobile Phone: +65-8369-2618

Need help with auto-titlebar on unmaximized window withCompiz/Ubuntu 11.04/Unity

2011-05-06T22:24:37

re, all.

Here's a bug filed against Google Chrome for the same problem:
http://code.google.com/p/chromium/issues/detail?id=80856 and here's some
forum users complaining about the same problem, and regrettably their
solution is to stop using Ubuntu's Unity mode:
http://ubuntuforums.org/showthread.php?t=1742354.

I work for VMware and for our Unity mode (which has the unfortunate name as
Ubuntu's new Unity mode), where we show individual guest Virtual Machine
windows in the Linux host environment as individual windows, we use
undecorated windows, similar to how Wine shows Windows applications in X
without having to be inside the full Windows desktop container. The problem
I'm trying to figure out a solution for is that when our user maximizes the
guest window and then unmaximizes it in Ubuntu 11.04's default Unity desktop
environment, Compiz is putting a titlebar onto our window just like it puts
one on Google Chrome.

Can you guys please help me understand why Compiz is doing this, if it's
something that Compiz is doing on its own or if it's Ubuntu's Unity stuff,
and how I can keep this from happening?

Thanks very much!!!

I can't get access to the Compiz forums: 403 - Forbidden

Rune K. Svendsen — 2011-05-01T18:41:48

Hi list

I'm trying to get access to the Compiz forums, but I am greeted with a
"403 - Forbidden"-page.

Is this a known issue?


Regards,
Rune

ccsm: Patch for autofocus on return to main page

Silvia Dobrota — 2011-02-17T17:32:06

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi guys!

This is my first patch for compiz.
I found it very annoying that when you filter for some plug-ins, click
on one of them and later come back to the main page, the filter entry is
not focused anymore so you have to click on it with your mouse, in order
to search for other plug-ins.

Thank you,
Silvia
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNXVuWAAoJEPYkGph0x7WujUcH/jl+FTSrJYO0EPe5LeLBKy05
Xm3w8WlGrlK7HY+ZpNghrlL4PuDUJfkyCUwmKlIRg4EqinmzagBQcjhDZv7d7bIF
9Zahrqmcbn6ZLT7z4J6+CN2ZJNzk+E/fYYOiXOEdRCfsYO6QqSP6X/ojq2wnm6QN
AqkkvDF9XEjQXle7rBtD7CjA96quOp4EHVtFPheTe+OP4eQ4+0ghP9fEBVOUco+i
7egk9PbUHn04DBWIfSX+olvbujMEQOODcpNWgxqg/k0l0Y0dwpCDIcVFu0aGR52U
usttwS2Upen1iaVW4wWwSjyh9O/i2ABOf50MnxtT65u25IjK3GH1cU84zwD68FA=
=Zu8s
-----END PGP SIGNATURE-----

[PATCH] Focus filter entry on return to main page

Silvia Dobrota — 2011-02-17T17:33:26

From 5801cf0fbacde51ec60664efb1dd675a725b0f99 Mon Sep 17 00:00:00 2001
From: Silvia Dobrota <sd3209< at >doc.ic.ac.uk>
Date: Thu, 17 Feb 2011 17:19:19 +0000
Subject: [PATCH] Focus filter entry on return to main page

---
 ccm/Window.py |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/ccm/Window.py b/ccm/Window.py
index 9478f34..1b57fcf 100644
--- a/ccm/Window.py
+++ b/ccm/Window.py
< at >< at > -96,6 +96,7 < at >< at > class MainWin(gtk.Window):

     def BackToMain(self, widget):
         self.SetPage(self.MainPage)
+        self.MainPage.filterEntry.grab_focus()

     def RefreshPage(self, updatedPlugin):
         currentPage = self.CurrentPage

Move KDE Plasma Integration to KDE Git Infrastructure

Martin Gräßlin — 2011-01-16T16:07:46

Hi Compiz developers,

as you might know KDE will transition to git somewhen next week. This gives 
some new possibilities for the Compiz community, too.

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 use a 
different window manager and has not removed any legacy code. This is a hughe 
advantage and although it does not look like other shells care about 
supporting different window managers I do not want to lose the possiblity to 
switch the window manager.

Up to now Compiz has done a great job of supporting our additions, so that 
Compiz users get the same level of integration as KWin users. Nevertheless due 
to the fact that releases are out of sync Compiz users do not get new features 
when KDE has a release. This gets to a real problem when KWin changes the 
decoration API as that causes KDE4-Window-Decorator to crash (this is the most 
often reported bug against KWin). This has let to a stagnation in our 
decoration API as we don't dare to touch the code again. Nevertheless I plan 
to change the API in 4.7 and our most prominent decorations (Oxygen and 
Aurorae) will move to it.

Now with the git transition there might be a solution for these kind of 
problems: Compiz's KDE Plasma integration is moved to KDE's infrastructure and 
could be released in sync with the rest of Plasma. This means you don't have 
to care about the release (done by KDE's release team). Additionally you get 
the advantages of the KDE community like the Krazy checks [1] and developers 
going through the code and fix common issues. Translation would be provided by 
KDE's translation infrastructure ensuring that the code is translated into all 
the languages KDE supports and providing a consistend translation.

Concerning better support for changes in Plasma/KWin integration and 
decoration API, there is the chance that KWin developers will directly port 
changes to Compiz if it is in the same repository. Especially the decoration 
API is that small that we can add support to Compiz directly.

Nevertheless there are a few things you should be aware of:
* Everybody with commit rights to KDE would be allowed to commit to it.
* You would need a KDE commit account to be able to commit to the repository 
(though KDE hands out commit rights rather easily and you are all proven 
members of the community)
* You would probably need to go through a two weeks Review Process which 
requires that there are no reported Krazy issues. Last time I looked into the 
Compiz KDE integration part the code was not in a state to get through review 
directly (As you are also using C++ I can only recommend to run KRazy checks 
on your main repository, too. It should also find generic options and KDE 
specific checks can be disabled.). Depending on where the repo will me moved 
that step might be omitted.

The last point gets me directly to where to move the code. There are several 
options:
1. Own repository either in extragear or as part of KDE SC. KDE SC would mean 
releases synced with rest of KDE.
2. Part of workspace repo. Same as option 1 with SC, but you get also access 
to the private libs of workspace. This means you could add support for KDE's 
activities, use Kephal for screen handling and could in general add more 
integration for Plasma. Disadvantage: KDE does not use submodules so the code 
needs to be imported, which means the code really has to move to KDE 
infrastructure.
3. Part of KWin. That is same as option 2, plus you could use KWin internal 
code. E.g. no need to duplicate decoration code any more, make use of KWin 
parts separated from core (e.g. Alt+Tab). This is probably the best 
integration you could get.

Personally I would prefer option 3 from an integration point of view. My 
current plans are to modulize KWin which would allow to make use of more KWin 
features.

If there is interest from your side for going such a step, I would contact 
KDE's sysadmins to evaluate a possible merge path.

Cheers
Martin Gräßlin
KWin Maintainer

P.S. We will probably have another Plasma developer sprint in Europe around 
April. It would be nice to have some Compiz developers around to discuss 
possible future integration and collaboration.

[1]: http://quality.kde.org
_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

Compiz Fusion and Linux Fusion

2010-12-05T20:00:58

Hi guys,
let me first introduce myself, I'm Fusion Linux (www.fusionlinux.org)
project leader.

Fusion Linux is a Fedora Remix that includes all the best software
that is available for Linux. Fusion uses a combination of free and
open-source, non-free and non-open-source firmware and software, to
bring the user the most advanced experience on the Linux platform.

Fusion Linux is 100% compatible with Fedora. A Fedora Remix including
packages from Fedora and RPM Fusion software repositories plus some
custom packages.

We would like to enable Compiz by default in our next release.

From what I have seen there are few Compiz configuration tools, right?
Which one do you recommend we include by default for non-advanced
users?

We would like to enable Compiz by default for our Live DVD and Live
USB versions automatically, which way is best to enable Compiz? Do we
need to edit some gconf options or just start compiz via terminal?

I would also like to include some great Compiz video that show of some
of the best Compiz features that enhance desktop usability and
productivity, so please send any links you have to that kind of
videos.

Thank you in advance,
Valent.

Upcoming structural changes to compiz core - HEADS UP

Sam Spilsbury — 2010-11-13T10:35:17

Hi Everyone,

I'm going to make some big structural cleanups to core which is likely
to affect everyone here, but I believe is for the better, so I am
posting this mail now to get some feedback and make sure that we don't
tread on anyone's toes when I merge all of this stuff.

1st Change: Decorators are going in their own repo
=========================================

The decorators are going to be taken out of core and put into
individual git repositories (/compiz/decorators/kde4-window-decorator
/compiz/decorators/gtk-window-decorator) so that we can work on them
individually. Making commits to core when working on these decorators
is annoying when it comes to bisecting other problems in core and in
the decorators themselves too, so we should just move them to separate
repos.

This also helps package maintainers in the long run, since they no
longer need to do 3 separate builds of compiz in order to get a
compiz-kde or compiz-gnome package

2nd Change: GNOME Integration stuff into it's own repo
==============================================

Again, same reasons as above. Also, stuff for gnome-control-center
doesn't belong in a desktop agnostic core and even though you can
disable it by default. And it makes packaging easier.

3rd Change: Moving the following plugins into plugins main
================================================

 * cube / rotate (one of the more well known ones, but still an effect)
 * wobbly

The above reasons and also the semi-obvious ones listed next to the plugins.

4th Change: Moving the following plugins in to plugins extra
================================================

 * annotate (it's for drawing on the screen, not managing windows)
 * blur (it's an effect)
 * ini / inotify (we recommend people to use compizconfig now, but
ini/inotify should still be available in case people don't want to use
it)
 * screenshot
 * water

Same reasons as above

5th Change: GConf Schema Generation moved out of core
================================================

Currently we generate GConf schemas for all the plugins in the
CompizPlugin.cmake buildsystem. Even though you can turn it off, I
still think that keeping this in core as a matter of principle is
wrong. Also, the rest of GNOME is moving from GConf to GSettings and
we will need to write a GSettings backend and GSettings schema
generation. I don't think that we should have both in core when that
happens.

I propose that we move the GConf schema generation into
compizconfig-backend-gconf's buildsystem and out of CompizPlugin. I
have already created a simple way to add build hooks to plugins [1] so
we will install a CompizGenGconfSchemas.cmake into
${PREFIX}/share/cmake/plugin_extensions, which when installed, will
automatically be processed any time a plugin is built (so that schemas
can be built for the plugin). Of course, this leaves the problem that
core needs to be built first and then compizconfig-backend-gconf and
then core again if you want to get the schemas, but I have also found
a solution for this as well, which allows the
compizconfig-backend-gconf to automatically generate schema files for
every single plugin which has already been installed.

6th Change: Split gtk-window-decorator into two decorators
================================================

As everyone probably knows, gtk-window-decorator is really two window
decorators in one - a simple window decorator which uses cairo to draw
a decoration which changes color based on the current highlight_color
of your gtk theme and also a window decorator which uses
libmetacity-private to render the decoration based on your current
metacity theme. If you don't want to build the metacity section, you
can just disable USE_METACITY on build.

This of course, is a mess.

I think that we should split these into two decorators, a cairo one
and a metacity one and have a shared libgdkcompizdecorator.so. This
probably won't happen until the next release though.

I'll do this in about 4 days, so please give me some feedback before I do.

Kind Regards,

Sam

[1] http://git.compiz.org/compiz/core/commit/?id=b45a3a77866e037c90f13f45537187bd8bb30f0f

[RFC] Draft for a compositing manager specification

Martin Gräßlin — 2010-08-15T12:57:28

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

Initializing active window lists in animation

Jay Catherwood — 2010-07-22T15:13:31

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

Compiz 0.9.0 is Released!

Sam Spilsbury — 2010-07-04T09:12:35

Compiz 0.9.0 is released!

This is the first unstable release of the Compiz
0.9 series. This release represents a complete rewrite of the 0.8 series from
C to C++, brings a whole new developer API, splits rendering into plugins,
switches the buildsystem from automake to cmake and brings minor functionality
improvements. This release represents the first developer and tester preview of
what will eventually make the 0.10.x stable series. Please note that as such, it
is not yet ready for general use as there are a number of known issues,
regressions and incomplete functionality.

The Compiz 0.9.0 tarballs are available at http://releases.compiz.org/0.9.0/ .
You can verify these tarballs using the sha1sums in
http://releases.compiz.org/0.9.0/compiz-0.9.0.sha1 , which are
signed by Compiz Release Team GPG key (C2B8F46E) at
http://releases.compiz.org/0.9.0/compiz-0.9.0.sha1.asc .
Please note that each component is also available in its own directory in
http://releases.compiz.org/components/ .

Quick changelog:

compiz-core:
------------
* Completely rewritten developer API in C++, using boost and stl to simplify a
  number of tasks originally handled in core.
* Reworked plugin function hooking system, where the WRAP / UNWRAP macros
  have been replaced with 'smart' function call chains using real function lists
  that can have any component turned off at any time to save unneeded CPU cycles
* Rendering framework split into the composite and opengl plugins, the former
  making compiz a compositing window manager and the latter performing that
  compositing using OpenGL. Such a split will allow new rendering plugins such
  as XRender and Clutter to be developed as well as for compiz to run as a
  non-compositing window manager
* Added copytex plugin, which re-implements part of the 'copy mode' texture
  binding from Beryl. While this is slower, it allows for textures that are
  larger than the maximum texture size allowed by the host's OpenGL
  implementation
* Added decoration reparenting to the decoration plugin. This will allow compiz
  to run with decorations as a non-compositing window manager.
  Reparenting support added to both gtk-window-decorator and
  kde4-window-decorator
* Added KDE Plugin to integrate with the QT main loop and create a KApplication,
  for further integration into KDE.
* Added compiztoolbox library plugin, allows developers to do tedious but
  repeated actions in many plugins such as set up the application switcher
  window and draw thumbnails of window
* Plugins rewritten in C++ using the new API
* DBus plugin now uses the screen number to identify compiz instance.
  This means that scripts which use /allscreens will no longer work.
  In general this means that paths have now changed to be
  /org/freedesktop/compiz/screen{screen_number}/ ...
  In a single instance of compiz, {screen_number} would generally be 0 (i.e
  screen0)
* Shape drawing implemented in annotate. Also fixed long standing damage bug
  that caused skips in line drawing.
* Added serialization interface to core, which allows plugins to save activity
  states on plugin load/unload and through compiz relaunches. The data is stored
  in X11 window properties and automatically dropped when relevant X11 resources
  are destroyed

plugins-main:
-------------
* Rewritten animations interface; supports object oriented animation
  construction, which should further simplify creating new animations
* Switchers support viewing only icons
* Added support to drag windows to edges and have them fill the adjacent side of
  the screen
* Plugins rewritten in C++ using the new API


plugins-extra:
--------------
* Added support for automatic wallpaper rotation
* Added edge support to grid plugin so windows can easily be resized by dragging
  to an edge or corner
* Plugins rewritten in C++ using the new API


plugins-unsupported:
--------------
* Rewritten elements interface - allows definition of elements in an object
  oriented fashion, easily create new plugins that hook into the existing
  functionality of the plugin
* Plugins rewritten in C++ using the new API


ccsm:
-----
* Number of buttons increased to 20
* Fixed bug newer gtk exposed where values were not read before destroying the
  dialog window resulting in blank entries


compizconfig-backend-gconf:
---------------------------
* CMake buildsystem


compizconfig-python
-------------------
* Distutils buildsystem


libcompizconfig:
----------------
* CMake buildsystem
* Plugins rewritten in C++ using the new API


Please note that there are new build dependencies for this release, including
boost-devel, cmake and cython. Additionally, libboost is a required
runtime dependency.

This is a development release and as such there will likely be bugs. Feel free
to report bugs at our bug tracker at http://bugs.opencompositing.org/. Currently
known issues are:
 * Miscompilation with GCC 4.5 resulting in the occasional crash on window
   closes or plugin unloads. Please compile with GCC 4.4, or see bug 1308[1]:
   for a workaround to compile with GCC 4.5
 * Some SDL applications like frozen-bubble and qemu will not display correctly.
   Please launch these applications in a window manager like metacity or kwin
   first and then switch back to compiz.

Compiz is entirely developed as a volunteer project, and we'd like to thank
everyone who contributed to this release. Translators, testers, the support team
and developers: thank you, your continuous contributions made it all possible.

We hope you will enjoy using Compiz as much as we enjoyed writing it!

- The Compiz Team

[1] http://bugs.opencompositing.org/show_bug.cgi?id=1308

Two patches for Snap

Jay Catherwood — 2010-06-18T05:42:03

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

putting to viewport in 0.9's Put plugin

Jay Catherwood — 2010-06-10T21:38:08

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

Using vpswitch with wall in 0.9

Jay Catherwood — 2010-06-10T03:23:31

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz

Shelf plugin ignores current deformation and places window only on 'cube' face during rotation?

David C. Rankin — 2010-05-31T20:30:33

Guys,

Here is a potential bug that may need to be looked at. If the scale plugin is
used and deformation is set to cylinder, then when the desktop is rotated, the
self-sized windows are shown on the face of the cube instead of on the face of
the cylinder. The sphere deformation has the same problem. It looks really odd.
Here are a couple of screenshots showing this behavior:

(1) screenshot of desktop showing windows shelved (102k):

    http://www.3111skyline.com/dl/bugs/compiz/scale-on-cube-only_01.jpg

(2) screenshot of cylinder rotation showing shelved windows still on cube face
and not on cylinder face (95k)

    http://www.3111skyline.com/dl/bugs/compiz/scale-on-cube-only_02.jpg

(3) screenshot of sphere rotation with shelved windows:

    http://www.3111skyline.com/dl/bugs/compiz/scale-on-cube-only_03.jpg

This is with the compiz 8.6 rpms from Dmitry on opensuse 11.0. I suspect it
doesn't matter what OS it is running on. Let me know if I can run any additional
test for you. Thanks.

Skydome suggestion for 9.0 or other future release

David C. Rankin — 2010-05-31T05:20:44

Guys,

One thing that could be improved with skydome when it is animated is to have it
'centered' behind desktop 1 when you initiate rotation or show the desktop wall,
etc. Many times when you want to take a screenshot, you naturally will want to
have the central feature of your skydome in view. If you have cubecaps, then the
orientation of the cubecaps gets all messed up when you rotate the cube to get
to the center of the skydome.

The options for 'adjust caps', clamp, etc., just don't really allow you to
accomplish this without causing further scaling/orientation problems for the
caps. (especially if the cap image is circular)

I finally got to where I would use gimp to flip the cap vertically and then
rotate CCW to have the caps orientated correctly. Centering the skydome behind
desktop 1 sure seems like an easier solution.

Obviously this is just something to consider. But when your product is based on
coolness -- this is a bit more to throw in top :p

small bug in 8.6 commands - grab key doesn't close after + Other good feedback

David C. Rankin — 2010-05-20T22:57:05

Guys,

Here is a little something to look at in the code. I have the following set:

Run command 1:  /opt/kde3/bin/ksnapshot<Super>Print
Run command 2:  /opt/kde3/bin/ksnapshot --current<Alt><Super><Sys_Req>

The bug occurs when you choose 'Grab key combination' for
<Alt><Super><Sys_Req>. When you enter the keystroke, the keystroke is clearly
accepted/interpreted by the grab key combination routine, but the little
rectangle that says "Please enter the new key combination" does not close after
the key combination is entered. See the screenshot:

(20k)
http://www.3111skyline.com/dl/bugs/compiz/altsupersysreq.jpg


This is most likely because of some of the 'ok, I got it' code doesn't
recognize the Sys_Req key, but the code that actually 'gets' the key combination
is perfectly happy with it.

As a workaround, all I did was manually close the dialog and the key
combination works fine. Everything else is working fine too. I'm still messing
with the timestep, but it is working pretty good. It might be worth looking at
what controls the number of revolutions per x-y distance of mouse motion.
Everything else is beautiful with the default settings. ( I always change a few
others for taste, but nothing wrong with the present defaults) Oops, I take that
back, the default deformation of cylinder with a zoom value of '0' does not
work. I don't know how the default deformation is chosen, but if the default
will always be a cylinder on a new install, then the zoom needs to be set at
40-50% (.4000-.5000) to keep the cylinder from having the "In your face" look on
rotation.

The only other request I have outstanding is whether I can adjust the aspect
ratio of the cylinder. In 8.6, it looks much more like a hockey-puck than a can.
See the following comparison of 8.2 versus 8.6 screenshots:

(8.2 - 100k)
http://www.3111skyline.com/dl/img/ss/compiz/compiz82_shots-00.jpg
(8.2 - 56k)
http://www.3111skyline.com/dl/img/ss/compiz/comiz-darkredplanet.jpg

(8.6 - 64k)
http://www.3111skyline.com/dl/img/ss/compiz/cmpiz-8.6-rot_03.jpg

In the past, the sphere ratio controlled the cylinder also, now it has no
effect and you are just stuck with the default cylinder aspect ratio. I would
prefer to be able to add a little height to make it look more like what is shown
in the 8.2 screenshots above. It wouldn't take too much, probably another 15-20%
in height would do. This also cuts down on the amount of zoom required to have
the cylinder fit nicely in the window. Any ideas how I can adjust the cylinder
aspect ratio? I have tried about every setting I can think of and I haven't been
able to change the ratio at all...

Compiz 8.6 on openSuSE 11.0 -- Success! But need help with a few issues.

David C. Rankin — 2010-05-19T02:49:50

Dominique, cc: compiz,

  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 themselves. 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, but I have a dozen or so that will not 'activate' for lack of better
words. (you check -> they uncheck 1-5 secs later)

My Hardware:

Toshiba 205d laptop, AMD Turion-58, 4G of Ram, 640G sata drive,
gpu: ATI Technologies Inc RS690M [Radeon X1200 Series]
driver: ATI fglrx 8.532 (ATI 8-9 Release)

My Software:

OS: OpenSuSE 11.0, x86_64, 2.6.25.20-0.7-default
Desktop: Gnome 2.22

20:20 alchemy:~/.config/compiz> rpm -qa | grep "compiz\|fusion" | sort
compiz-0.8.6-46.1
compiz-branding-openSUSE-0.8.6-46.1
compizconfig-settings-manager-0.8.4-3.2
compiz-emerald-0.8.2-2.2
compiz-emerald-themes-0.6.0-16.1
compiz-gnome-0.8.6-46.1
compiz-kde-0.8.6-46.1
compiz-plugins-extra-0.8.6-5.2
compiz-plugins-main-0.8.2-100.1
compiz-plugins-unsupported-0.8.2-100.1
fusion-icon-0.0.1_080201-7.1
libcompizconfig-0.8.4-3.2
python-compizconfig-0.8.4-9.2

The compiz config generated during testing:

http://www.3111skyline.com/dl/bugs/compiz/compizconfig-8.6.tar.bz2

  Strange, 8.6 intentionally ignored my existing config in
~/.config/compizconfig and created a new configuration in
~/.config/compizconfig-1, which was fine because it left my 8.2 config as a
reference. If interested, the 8.2 config is here:

http://www.3111skyline.com/dl/bugs/compiz/compizconfig-8.2.tar.bz2

  The first issue I notice with compiz 8.6 was slow rotation when using the
mouse to rotate the cube, cylinder, sphere and that the aspect ratio of the
cylinder was more hockey puck like than usual. There were blurs or pixelations
around the top edge of the cylinder that were noticeable as pixelation of the
top 2 lines of the screen when switching faces with the keyboard and were
readily visible in the screenshot of the cylinder:

(45k - previously posted to the compiz list)
http://www.3111skyline.com/dl/img/ss/compiz/topPixelation-crop.jpg

  The slow rotation was noticed when I initiated the rotation, and swept my
mouse all the way to it's normal left range of motion and only had 1/2 rotation
of the cylinder. What I did was to adjust 'Timestep' to try and correct the
issue and had some success. Details:

    Setting: Rotate Cube -> Timestep = 1.8 restores default rotation speed, but
causes overrun on keyboard 'Next/Previous Desktop' (ctrl+alt+right/left)

    Setting 'Timestep = 1.2' is a workable compromise.

  This was somewhat similar to the 8.2 issue where rotation with the keyboard
looked as if it was in slow motion. In 8.2, it was about a 2-3 second process
for ctrl+alt+left, zoom cube, flip to desktop (wiggle a bit), unzoom, then
wiggle into place to complete the flip. Similarly playing with the settings
(endlessly) got it as close as it was going to get. As mentioned in my earlier
post, the 8.6 response in this area is MUCH better.

The Non-Working Features (I set, then magically they unset)

  Here is where I need the most help. In 8.6 there are a LOT of features/options
that don't work. Here is a summary of what won't stay set for me. This came from
my run-through of the settings and is probably 90% complete. Some I couldn't try
because it would have disabled others like 'Show Desktop' and 'Fade Desktop' or
Viewport Switcher which I don't use. I did try all but about 3-4 options. These
were all working this morning on my box with the same hardware/software config
in compiz 8.2:

    Accessibility (non-working): Opacify, Show Mouse, (mouse polling)

    Desktop (non-working): Expo  (I really miss Expo)

    Effects (non-working): Analglyphs, Animations, Animations Addons, Cube 3D,
Cube Atlantas, Snow Globe, Photowheel   (likewise -- I really miss Photowheel)

    Utility (non-working): Resize Info, Scale Addons, Work Arounds

    Window Management (non-working): Put, Ring Switcher, Shift Switcher, Static
Application Switcher, Tile

  What I can't figure out is how can 'Cube Gears' work, but not 'Photowheel'?? A
screenshot of the current 8.6 setup:

(64k)
http://www.3111skyline.com/dl/img/ss/compiz/cmpiz-8.6-rot_03.jpg

  Compiz 8.2 with everything working in a similar config (taken yesterday):

(102k)
http://www.3111skyline.com/dl/img/ss/compiz/dcrBlueDarknessLight.jpg

  Also, how can I get the aspect ratio of the cylinder back to what it looked
like in the 8.2 screenshot above. IIRC, the aspect ratio setting for the sphere
also controlled the cylinder in 8.2. I've tried that in 8.6 and it doesn't any
more. Any thoughts?

  Guys, where I really need your thoughts and help is with all the options that
won't stay set. My hardware/software config is the exact same as in 8.2, but
now, the settings outlined above don't want to play nicely anymore. What should
I check? What about the 8.4/8.6 package mix?

  Lastly, great job Dominique with getting 8.6 built for openSuSE 11.0 and Sam,
All, great job with compiz 8.6. Like I said at the beginning, 8.6 is working
beautifully in all aspects accept what I've outlined above. I know the issues
probably have something to do with the 8.4/8.6 mix of packages I have installed
or a setting or compile option that just needs to be ironed out. But if these
are the only issue to deal with, and no white or black screens, etc., it looks
like 8.6 is a home-run!

P.S. Dominique, even though emerald wasn't built as part of this set of rpms,
the 8.2 version continues to work great!

Compiz 8.6 - suse 11.0 1-2 rows pixilation at top of screen on kbd rotate

David C. Rankin — 2010-05-18T21:12:25

Listmates,

This is no biggie, 8.6 is working well so far. However, I do notice 1-2 lines
of pixelization at the top of the screen on keyboard rotate. I know this hasn't
been there since the 0.5.6-0.6 days when compiz was first released for opensuse
years ago. It wasn't there up through 8.2. The gpu is the radeon X1200 using the
fglrx-legacy driver.

Looking at the screenshot it actually looks like it is a pixelization issue
with the top edge of the cylinder.  Here is a screenshot. Look around the top
rim of the cylinder, you can see mini white spots or triangles around the top edge:

(46k)
http://www.3111skyline.com/dl/img/ss/compiz/topPixelation-crop.jpg

Also, initial looks at 8.6 it works great. The only issue I've stumbled on yet
is the initial mouse rotate speed with 'Timestep = 1.0000'. If I set Timestep =
1.8, the old rotate speed is back, but it causes the over-rotation on keyboard
rotate to next/previous side. A compromise value of Timestep = 1.2000 seem to
work okay. Rotation is a bit slow, but you get 1-revolution with normal
left/right mouse range of movement and the over-rotation on keyboard rotate
isn't that noticeable. I had fits with the over-rotation and then 'wiggle' into
place on keyboard rotate in 8.2. This is MUCH better, but could use a bit of
tweaking. I'll play with the settings a bit more and see if I can find a better
combination.

What would really help there, would be something that tells me what the
relationships are between the setting like Timestep, speed, etc.. Does some type
of schematic for that logic exist? It has always been just a guessing game for
me in the past, not knowing how sensitive one setting is compared to another or
whether adjusting any two of the settings works to cancel what I'm trying to
achieve...

If something like that exists, please let me know and just send a url. Also, if
I can provide any more info, also let me know. Great job guys!

Aurorae for Compiz

Martin Gräßlin — 2010-05-16T15:16:36

_______________________________________________
compiz mailing list
compiz< at >lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz