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 108208 - Suggest not showing registers window by default
Suggest not showing registers window by default
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Rich Burridge
Rich Burridge
Depends on:
Blocks:
 
 
Reported: 2003-03-12 16:51 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2003-03-12 16:51:17 UTC
It'd be nicer perhaps if this window was hidden by default; you have the
dropdown in the store/recall/exchange buttons anyway.
Comment 1 Rich Burridge 2003-03-12 18:50:53 UTC
The very first time that you bring gcalctool up, you
do not get memory registers. But gcalctool will remember
certain state information, one of which is whether you last
had memory registers showing. The next time you start gcalctool,
(if you had the register window open), it will be displayed.
This (and the other state settings) are described in the 
online help.

Cc:'ing Calum for his input on this.
Comment 2 Havoc Pennington 2003-03-12 22:16:35 UTC
I definitely agree it should remember your previous state - perhaps 
I had state left over from trying it a long time ago.
If it's not there by default that's all I was suggesting,
can close the bug.
Comment 3 Rich Burridge 2003-03-13 01:02:20 UTC
Just to double check I did:

% rm -rf ~/.gconf/apps/gcalctool
% gcalctool

and gcalctool came up with no initial memory register window.

Closing as not a bug. 

Thanks.
Comment 4 Rich Burridge 2003-03-18 11:17:40 UTC
Reopening. Dennis Cranston discovered that the gcalctool
schemas file had the default value for the "showregisters"
resource set to true. Gotta fix that.
Comment 5 Rich Burridge 2003-03-18 11:21:18 UTC
Change made. Fixed in v4.2.73. Thanks Dennis.