Bug 443610 - RFE: disable "Zoom Out" button in corner
RFE: disable "Zoom Out" button in corner
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kdebase-workspace (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Kevin Kofler
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-22 11:13 EDT by Mary Ellen Foster
Modified: 2008-04-28 11:59 EDT (History)
3 users (show)

See Also:
Fixed In Version: 4.0.3-18.fc9
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-28 11:59:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mary Ellen Foster 2008-04-22 11:13:13 EDT
Description of problem:
Until "containments" actually exist, the "Zoom Out" button in the corner of a
KDE workspace doesn't actually do anything useful -- in fact, clicking on it can
produce the impression that you've broken your desktop and, if you zoom out
enough times, it's difficult to find the buttons to click on to zoom back in. It
would be nice to disable that button for the time being until it actually has a
useful function.
Comment 1 Lukáš Tinkl 2008-04-22 11:22:50 EDT
http://websvn.kde.org/?view=rev&revision=794496

This patch from SUSE's branch contains what we need, up for discussion; I'll 
take care of it once we decide
Comment 2 Kevin Kofler 2008-04-22 11:44:00 EDT
I put it onto the agenda for today's meeting earlier today, so we'll discuss 
this in a few minutes. :-)
Comment 3 Kevin Kofler 2008-04-22 11:44:30 EDT
(By the way, the openSUSE patch is a one-line addition. Disabling stuff is 
usually easier than adding it. ;-) )
Comment 4 Jon Stanley 2008-04-23 16:30:11 EDT
Adding FutureFeature keyword to RFE's.
Comment 5 Kevin Kofler 2008-04-28 11:59:28 EDT
kdebase-workspace-4.0.3-18.fc9 tagged f9-final.

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