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 392942 - Alternate view->freeze specification.
Alternate view->freeze specification.
Status: RESOLVED DUPLICATE of bug 594875
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other All
: Normal enhancement
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-01-04 23:35 UTC by A
Modified: 2009-11-11 23:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description A 2007-01-04 23:35:47 UTC 
Please describe the problem:
doesn't work right when highlighting multiple rows or columns beginning at the origin

Steps to reproduce:
1.do either step 1a. or 1b.
1a.highlight entire column A and B
1b.highlight entire row 1 and 2
2.view > freeze panes



Actual results:
panes put in wrong place:

      F|G
16
---
17

Expected results:
a pane division would appear between col B and C or row 2 and 3 depending what direction you are trying to do

Does this happen every time?
yes

Other information:
also happens on selections greater than 2 rows or 2 columns
Comment 1 Morten Welinder 2007-01-05 01:44:03 UTC 
That's not a bug, actually.

The function of view->freeze is to make a split just above and to the left
of the selection.

As a special case, if A1 is selected, it will split in the middle so you can
drag the split to where you want it.  (Using the handles near the scroll bars.)

You are seeing the special case.

Now I can see that it would be useful to do something else if a range like
A:X or 1:n is selected.  Therefore I will leave it open as an enhancement
request.

Maybe just split to the right of the selected columns or below the last
selected row.
Comment 2 Andreas J. Guelzow 2009-11-11 23:09:16 UTC 
We have fixed this a short while ago (as the result of a duplicate bug report.)

*** This bug has been marked as a duplicate of bug 594875 ***