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 57746 - Undo/Redo buttons are sensitive, even if there's nothing to undo/redo
Undo/Redo buttons are sensitive, even if there's nothing to undo/redo
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2001-07-18 23:27 UTC by Zbigniew Chyla
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zbigniew Chyla 2001-07-18 23:25:50 UTC 
Package: Gnumeric
Severity: minor
Version: 0.68
Synopsis: Undo/Redo buttons are sensitive, even if there's nothing to undo/redo
Bugzilla-Product: Gnumeric
Bugzilla-Component: GUI

Description:
On startup both buttons are insensitive (which is good), but after clicking
f() button and then closing function selector window all toolbar buttons
are made sensitive _including_ Undo and Redo.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-07-18 19:25 -------

Reassigning to the default owner of the component, jgoldberg@home.com.
Comment 1 Almer S. Tigelaar 2001-07-20 09:53:07 UTC 
This is probably only the case for the bonobo build, we are disabling
the bonobo toolbars on input an re-enabling them afterwards.
Unfortunately that re-enables everything including the undo and redo
buttons. Probably we need to remember the state of all buttons and
restore that afterwards, but that seems very ugly.
Comment 2 Jody Goldberg 2001-09-06 01:06:26 UTC 
As suspected bonobo was being a bit odd in its notion of container sensitivity.  I have kludged around this for the specific case of undo/redo.  None of the other widgets change state.