Bug 52329 - FORMATTING: FILEOPEN reverts Row Height to optimum
Summary: FORMATTING: FILEOPEN reverts Row Height to optimum
Status: RESOLVED DUPLICATE of bug 52393
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.0.2 rc
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-21 03:15 UTC by Claude
Modified: 2012-07-24 09:25 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Intended settings of row height default font (19.54 KB, application/pdf)
2012-07-21 03:15 UTC, Claude
Details
Changes due to saving and opening file. (19.40 KB, application/pdf)
2012-07-21 03:17 UTC, Claude
Details
Intended row heights with different font sizes (19.77 KB, application/pdf)
2012-07-21 03:17 UTC, Claude
Details
Changes on saving and opening file (different font sizes) (19.93 KB, application/pdf)
2012-07-21 03:18 UTC, Claude
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Claude 2012-07-21 03:15:56 UTC
Created attachment 64474 [details]
Intended settings of row height default font

Verison 3.6.0.2 rc
Windows XP SP3; Windows 7

Trial 1:
Open a new spreadsheet.
Place some text in trhee separate rows, default font and font size (Arial 10)
Set row heights:  Row 1  1,0 cm;  Row 2: 1,5 cm;  Row 3: 0,47 cm  (Default)
Aspect as shown on attachment Trial_1_Expected.pdf
Save file

Open saved file
The row height has changed to the optimum size value:
Row 1; 0,45 cm;  Row 2: 0,45 cm; Row 3: 0,45 cm
As shown on attachment AfterSAvingandOpening_Trial_1.pdf


Trial 2:
Open a new spreadsheet.
Place some text in trhee separate rows, using different font sizes
Row 1:  Arial 14;  Row 2: Arial 16;  Row 3 : Arial 10 (defult)
Set row heights:  Row 1  1,0 cm;  Row 2: 1,5 cm;  Row 3: 0,47 cm  (Default)
Aspect as shown on attachment Trial_2_Expected.pdf
Save file

Open saved file
The row height has changed to the optimum size value:
Row 1; 0,62 cm;  Row 2: 0,71 cm; Row 3: 0,45 cm
As shown on attachment AfterSAvingandOpening_Trial_2.pdf


This behaviour came up on Libo 3.6.0.2;  It was not present in version 3.6.0.1
Comment 1 Claude 2012-07-21 03:17:00 UTC
Created attachment 64475 [details]
Changes due to saving and opening file.
Comment 2 Claude 2012-07-21 03:17:54 UTC
Created attachment 64476 [details]
Intended row heights with different font sizes
Comment 3 Claude 2012-07-21 03:18:47 UTC
Created attachment 64477 [details]
Changes on saving and opening file (different font sizes)
Comment 4 billhook 2012-07-23 03:52:52 UTC
Confirmed this behaviour on 3.6.0.2
Comment 5 Rainer Bielefeld Retired 2012-07-24 07:25:46 UTC
@billhook
<https://wiki.documentfoundation.org/BugTriage#Process>  item 5!
Please contribute more results: What is you OS, with what document did you get what results exactly, please contribute a 3.5 created document showing the problem with 3.6
Comment 6 Rainer Bielefeld Retired 2012-07-24 07:55:20 UTC
NOT [Reproducible] with Server Installation of  "LibreOffice 3.6.0.2 rc  German UI/Locale [Build-ID:  815c576] on German WIN7 Home Premium (64bit) 

Steps I tried:
1. opened new Spreadsheet
2. typed "a" into A1
3. A1: Charackter Arial size 20
4. Row 1 height 40 (does not matter whether drag and drop row heading border
   or with Format menu)
5. Save document / Close
6. Reopen document with 3.6, view seems to confirm report, but when you open
   document with 3.5.5 you see that in this version row height still is 40

So the only existing problem is "Bug 52393 - FILEOPEN 3.5.x spreadsheet with wrong row height"

Due to my results this one is INVALID or DUP of Bug 52393 - FILEOPEN 3.5.x spreadsheet with wrong row height

@ Claude:
Thank you for your attention!
Please feel free to reopen this bug if you find well founded indications a real, independent  row height FILESAVE bug exists with 3.6 and  you can contribute requested additional information due to <http://wiki.documentfoundation.org/BugReport> (especially BugReport Details)!

*** This bug has been marked as a duplicate of bug 52393 ***
Comment 7 Rainer Bielefeld Retired 2012-07-24 09:25:44 UTC
Modify Summary to avoid misunderstandings