After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157757 - Scrollbar shouldn't be present unless it's needed
Scrollbar shouldn't be present unless it's needed
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Sami Pietilä
Sami Pietilä
: 138875 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-11-09 14:55 UTC by Rich Burridge
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rich Burridge 2004-11-09 14:55:50 UTC 
The horizontal scrollbar, below the display area shouldn't be
present unless it's needed.
Comment 1 Rich Burridge 2004-11-09 15:51:37 UTC 
I've just discussed this with Calum. He suggests completely
removing the scrollbar. You should still be able to get to
the non-visible part of the text field.
Comment 2 Rich Burridge 2004-11-11 22:50:41 UTC 
Well it turns out that the "You should still be able to get to
the non-visible part of the text field" only seems to work
with GtkEntry widgets, so I've changed this, so that the scrollbar
isn't visible unless it's needed. I've also adjusted it so that
the rightmost part of the display area is always visible when you
are entering new input.

Changes checked into CVS HEAD. Bumped the version number
in configure.in to 5.5.12.
Comment 3 Sami Pietilä 2004-11-13 00:05:07 UTC 
The fix seems to be almost identical to what I used when trying to fix pr138875.

See pr138875, comment #7. The described problems occur in gcalctool 5.5.12.
Comment 4 Rich Burridge 2004-11-13 00:23:17 UTC 
Sorry, didn't realize there was already a bug open against 
this problem. Looks like you can close bug #138875 as a 
duplicate of this one.
Comment 5 Sami Pietilä 2004-11-13 09:47:11 UTC 
*** Bug 138875 has been marked as a duplicate of this bug. ***