Bug 21247 - Workspace and Viewport clarification in Swafish window manager ==> Workspaces config
Workspace and Viewport clarification in Swafish window manager ==> Workspaces...
Product: Red Hat Linux
Classification: Retired
Component: sawfish (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Havoc Pennington
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2000-11-22 10:48 EST by Michael McConachie
Modified: 2013-09-02 01:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-09 13:37:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael McConachie 2000-11-22 10:48:34 EST
In the Workspaces configuration window of Gnome Control Center, how about
adding a little bit of explanation to differentiate between Workspaces and
Viewports?  Something as minor as placing "Split each workspace into
viewports" between the Workspaces field and the Columsna dn Rows fields
should to it.

This would help make it more obvious that workspaces are a collection of

Comment 1 Elliot Lee 2001-02-08 15:43:15 EST
This is actually a sawfish problem, since the Sawfish capplet is contained in
that package. Just shuffling over.
Comment 2 Havoc Pennington 2001-02-08 18:19:59 EST
Sure, sounds fine. This isn't the kind of thing we usually put in Red Hat
specific patches, but I've mentioned the issue to the upstream maintainers of
Comment 3 Michael McConachie 2001-02-09 13:37:03 EST
Cool 'nuf. Thanks.

Comment 4 Havoc Pennington 2001-07-05 22:50:58 EDT
Hmm, we've been discussing this issue recently. Consensus is that having both
workspaces and viewports is a hopelessly braindamaged idea from a user interface

Anyhow, closing the RH bug, since it's been suggested upstream and will
hopefully get addressed there.

Note You need to log in before you can comment on or make changes to this bug.