Bug 75112 - borders in IDEAl mode are not "active"
Summary: borders in IDEAl mode are not "active"
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kmdi (show other bugs)
Version: SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Matt Rogers
URL:
Keywords:
: 83356 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-13 00:39 UTC by Gioele Barabucci
Modified: 2005-03-04 00:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gioele Barabucci 2004-02-13 00:39:35 UTC
Version:           3.0.0 (using KDE 3.2.0, Gentoo)
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r4, propolice)
OS:          Linux (ppc) release 2.4.22-ben2-r4

In IDEAl mode and fullscreen, if you move the mouse to the leftmost pixel, the buttons on the left are clickable; but if you move the pointer to the rightmost pixel, then the buttons on the right are not clickable (they are not focused).
Same problem appears with bottom border when statusbar is disabled.

This bug goes against Fitts' Law "NEVER put a one-pixel non-clickable boundary around buttons on the screen edge" http://developer.kde.org/documentation/design/ui/fittslaw.html

I suppose that this bug is unrelated to win-decoration/style, I tryed all the most common ones and they all shows the same problem.
Comment 1 Jens Dagerbo 2004-02-13 09:25:21 UTC
Couldn't agree more. Actually, I think the should be "at the border" even when the app is just maximized.

In which case this is something for kmdi. Reassigning.
Comment 2 Jens Dagerbo 2004-06-14 20:04:18 UTC
*** Bug 83356 has been marked as a duplicate of this bug. ***
Comment 3 Dominik Haumann 2004-08-28 17:06:10 UTC
This behavior is available for the Left and Right tabbar in Fullscreen-ideal mode for KDE 3.4 or even KDE 3.3.1.
Though on bottom there is still 1 pixel space, so on the very bottom the tabs are still not clickable.

If the application is maximized there is still the window border, so no chance to have *no* border.
Comment 4 Dominik Haumann 2005-03-04 00:16:25 UTC
CVS commit by dhaumann: 

This patch does the following
- implement splitterKeepSize correctly.
- Internally use always highResolution due to *ugly* rounding bugs.
- in fact, the high resolution mode never worked 100%. KDockWidget
  always assumes a splitter position between 0..100 but it was 0..10000,
  which lead to size-bugs undock/redock actions.

For KDE 4, remove this highResolution option completely.
This patch should be BC, kdockwidget_private.* is private API.

Compatibility: The splitter position must be always between 0..100.
If it is >100, it assumes high resolution from the old behavior, and
it will be fixed to a correct value between 0..100. This makes sure
it works for both, high resolution and not high resolution.

I tested this with k3b, kate, konqueror and a bit Quanta.
If you find bugs, please let us know on kmdi-devel@kde.org.

This fixes the bugs
- #69895: selection menu gets not properly positioned on the right side
- #75112: borders in IDEAl mode are not "active"

CCBUG:69895
CCBUG:75112

CCMAIL:kmdi-devel@kde.org


  M +13 -6     kdeui/kdockwidget.cpp   1.171
  M +7 -0      kdeui/kdockwidget.h   1.103
  M +295 -187  kdeui/kdockwidget_private.cpp   1.54
  M +128 -9    kdeui/kdockwidget_private.h   1.32
  M +28 -28    kmdi/kmdidockcontainer.cpp   1.72
  M +4 -4      kmdi/kmdi/dockcontainer.cpp   1.10



Comment 5 Dominik Haumann 2005-03-04 00:20:17 UTC
My above commit fixed this.
Comment 6 Dominik Haumann 2005-03-04 00:20:38 UTC
*** Bug has been marked as fixed ***.