Issue 110261 - Defect detected for [Window]-[Freeze] in scalc OOv3.2.0m12.
Summary: Defect detected for [Window]-[Freeze] in scalc OOv3.2.0m12.
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: viewing (show other issues)
Version: OOO320m12
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-19 15:24 UTC by cbiscione
Modified: 2013-08-04 08:43 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description cbiscione 2010-03-19 15:24:54 UTC
Hi, wOOrld,

There is a defect in the [Window]-[Freeze] feature on the scalc application.
It´s easyly reproduceable and i have tested and confirmed it in several scalc files.
To reproduce it:
1.- Open a new spreadsheet with scalc.
2.- Write something into cell J20, for example a number 1.
3.- Be sure to let the cursor located at cell J20.
4.- Go to the Window menú and select [Freeze].
5.- Slide right (zoom in) the zoom slider (located in the far bottom right on
the scalc window) until the J20 cell disappears of the visible work area.
6.- Slide back left (zoom out) the zoom slider to make cell J20 visible again.

Consecuences:
1.- The freeze window guides dissapear, the window is not frozen at the point it
should be and the checkmark in the [Window]-[Freeze] menu option is unchecked.
2.- If the work area is zoomed in just enough to see the horizontal freeze
guide, but not the vertical freeze guide, and then zommed out back, only the
horizontal freeze guide is drawn, the window is frozen only vertically and the
checkmark in the [Window]-[Freeze] menú option is still checked.

This behavior can not be a feature because it is reverting a decision made by
the user(s) of the spreadsheet.

I noted this at first on Open Office 3.1.0, so i installed Open Office 3.2.0
just to be sure that this was not corrected on the transition to v3.2.0m12.
Comment 1 Edwin Sharp 2013-08-04 08:43:22 UTC
As given in description.

Rev. 1507307 Win 7