Metacity switch workspace keys should be migrated to plane/wall

[Scott James Remnant (Canonical)]

Binary package hint: compiz

The keys used in metacity to navigate, move windows between and switch between workspaces should be migrated to compiz's plane/wall plugins to perform the same operation between viewports

[Scott James Remnant (Canonical) (canonical-scott)]

(Critical: composite-by-default blocker)

[Travis Watkins (amaranth)]

compiz (1:0.5.0+git20070516-0ubuntu2) gutsy; urgency=low

  * 011_snap-by-default.patch:
    014_fix-no-border-window-shadow.patch:
    080_cube_settings_for_ubuntu.patch:
    083_change_wobbliness_settings.patch:
    093-add-toggle-window-on-all-desktop.patch:
    - Dropped, no longer needed.
  * 017-disable-child-window-clipping.patch:
    - Renamed to 010-disable-child-window-clipping.patch
  * 081-restart.patch:
    - Renamed to 011-restart.patch
  * 088-gnome-bridge-keybindings-plugin.patch:
    - Renamed to 012-gnome-bridge-plugin.patch
    - Make metacity workspace movement keys map to plane movement keys
      (Fixes LP: #116824)
    - Map maximized_vertically and friends map to their toggle_* versions in
      compiz (Fixes LP: #116819)
  * 091_add-cursor-theme-support.patch:
    - Renamed to 013-add-cursor-theme-support.patch
  * 094-fix-gtk-window-decorator-no-argb-crash.patch:
    - Renamed to 014-fix-gtk-window-decorator-no-argb-crash.patch
  * Change shadow_radius to 9 to prevent white shadows on DRI drivers
    (Fixes LP: #116829)

 -- Travis Watkins <email address hidden> Thu, 31 May 2007 21:43:04 -0500

[Nanley Chery (nanoman)]

* Tested in Ubuntu 8.04.1 & [Intrepid]
The number of metacity rows stay constant when ported over to compiz, but compiz only uses the top-most row rather than all.
Steps to reproduce:
1. In metacity, choose: 2+ rows and four workspaces
2. Switch to compiz

[Adam Niedling (krychek)]

Nanley: If this is still a bug for you then you should have set it to 'new' instead of 'incomplete'.

[Hew (hew)]

Re-marking this as fixed since the issue as originally reported is different to Nanley's issue, which is definitely not classed as critical.

Nanley: Please report your issue as a new bug, thanks.