Bug 99158

Summary: Metacity needs wireframe window move
Product: [Retired] Red Hat Linux Reporter: Laurence Tyler <lgt>
Component: metacityAssignee: Havoc Pennington <hp>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-07-15 15:07:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Laurence Tyler 2003-07-15 12:27:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314

Description of problem:
Request for enhancement: Metacity does not have a wireframe window move option:
only opaque move is allowed. This is very irritating on a slower machine, and
especially for people like myself who habitually use wireframe move on other
systems.

I understand this very feature has been the subject of heated debate on the
developer's mailing list. There appear to be patches available to add a
wireframe window move and I wonder if this could be included in a RedHat update
for Metacity.

The new option should be reflected in the Preferences->Windows configuration tool.



Version-Release number of selected component (if applicable):
metacity-2.4.34-3

How reproducible:
Always

Steps to Reproduce:
1. Log in to RH 9 with default window manager
2. Drag any window around - note that it moves opaquely, redrawing all the time.
3. Select Menu->Preferences->Windows. Note that there is no option to select
wireframe window moving. 

Actual Results:  Stuck with opaque window moving :-(

Expected Results:  Should have an option for wireframe window moving in
Preferences->Windows

Additional info:

Comment 1 Havoc Pennington 2003-07-15 15:07:23 UTC
There's already a bug for this on bugzilla.gnome.org

I handle metacity bugs on both bug trackers, so there's no value to 
having one on both. ;-)