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 167479 - Memory register window visible in Basic mode.
Memory register window visible in Basic mode.
Status: RESOLVED FIXED
Product: gnome-calculator
Classification: Core
Component: general
5.5.x
Other All
: Low minor
: ---
Assigned To: Rich Burridge
Rich Burridge
Depends on:
Blocks:
 
 
Reported: 2005-02-15 15:26 UTC by Rich Burridge
Modified: 2005-03-10 17:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to resolve this bug. (1.50 KB, text/plain)
2005-03-10 17:08 UTC, Rich Burridge
Details

Description Rich Burridge 2005-02-15 15:26:17 UTC
It's possible for the memory register window to be
made visible when the user is in Basic mode, even though
they can't get/set the values of the memory registers.

This is not consistent.
Comment 1 Rich Burridge 2005-03-07 21:01:29 UTC
Just starting to think about gcalctool fixes
for GNOME 2.11/12.

Adding Calum to the interest list for this bug
for his opinion.

My plan is to make the View->Memory Registers
menu item inactive if the user is in Basic mode.

Calum, does that seem reasonable?
Comment 2 Calum Benson 2005-03-09 17:17:24 UTC
Certainly as long as you can't do anything with the memory registers in Basic
mode, the menu item shouldn't be available.

In future, I suppose one possibility might be to make the memory registers
somehow gettable/settable/editable from the memory register window itself, which
would mean you wouldn't necessarily require the Sto/Rcl buttons to be visible
before you could make some use of them.  In that case, I wouldn't have any great
objection to the window being available in Basic mode if people found the memory
functionality useful-- even basic real-world calculators usually have a simple
memory store/recall function.
Comment 3 Rich Burridge 2005-03-10 17:08:23 UTC
Created attachment 38516 [details]
Patch to resolve this bug.
Comment 4 Rich Burridge 2005-03-10 17:11:46 UTC
Fix checked into CVS HEAD. Version number in configure.in
bumped to 5.6.2.