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 496304 - Jumping to hidden sheet should not be allowed
Jumping to hidden sheet should not be allowed
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other All
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-11-12 23:45 UTC by sum1
Modified: 2007-11-15 03:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2007-11-12 23:45:15 UTC 
Version: r16117
OS: Ubuntu Gutsy

Steps to reproduce:
- Run Gnumeric
- Edit > Sheet > Manage Sheets
- Hide and reverse the direction of Sheet3
- Press OK
- Where it says "A1", type in Sheet3!Print_Area and press enter
- Notice that Sheet2 switches direction
Comment 1 Morten Welinder 2007-11-13 00:09:36 UTC 
Well, it is really Sheet3 you are seeing, but how in the world do you come
up with these test cases?

Clearly we should not display Sheet3 when it is supposed to be hidden.
Comment 2 Morten Welinder 2007-11-13 03:04:02 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 3 sum1 2007-11-14 21:43:58 UTC 
The original bug is fixed, but a similar one remains with r16135.

Steps to reproduce:
- Run Gnumeric
- Edit > Sheet > Manage Sheets
- Hide and reverse the direction of Sheet3
- Press OK
- Where it says "A1", type in Sheet3!Print_Area and press enter
- Press OK on the "Cannot Jump..." message box that appears
- Undo
- Redo
- Notice that Sheet2 looks like it switched direction
Comment 4 Morten Welinder 2007-11-15 02:56:15 UTC 
Unrelated -- you can skip the jump step.  But yes, this needs to be fixed.
Comment 5 Morten Welinder 2007-11-15 03:37:16 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.