Bug 78674 - FORMATTING - Calc ignores manual breaks when "Fit print range(s) to row width/heigth"" fit print range(s) on number of pages" is chosen
Summary: FORMATTING - Calc ignores manual breaks when "Fit print range(s) to row width...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.0.0.alpha0+ Master
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-05-13 21:24 UTC by m_a_riosv
Modified: 2014-05-17 00:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample file to test (14.85 KB, application/xml)
2014-05-13 21:24 UTC, m_a_riosv
Details

Note You need to log in before you can comment on or make changes to this bug.
Description m_a_riosv 2014-05-13 21:24:19 UTC
Created attachment 98996 [details]
Sample file to test

In https://bugs.freedesktop.org/show_bug.cgi?id=40788, was fixed the use of manual page breaks in all option of the scale output for page style.

Verifying it, I had reported my observations in that bug comment#55.

Verified for the three scale options with:
Win7x64Ultimate:
Version: 4.2.3.3 Build ID: 882f8a0a489bc99a9e60c7905a60226254cb6ff0
Versión: 4.2.4.2 Id. de compilación: 63150712c6d317d27ce2db16eb94c2f3d7b699f8
Version: 4.2.5.0.0+ Build ID: c4e10ad83fe1fa92a115327c1909218f5dc8c8bd
   TinderBox: Win-x86@42, Branch:libreoffice-4-2, Time: 2014-05-12_10:29:35

But doesn't work for me with a clean profile in:
Version: 4.3.0.0.alpha1+ Build ID: 224b235971a01971de626d38ccc8506d0a55771b
   TinderBox: Win-x86@39, Branch:master, Time: 2014-05-11_23:55:10
Only works for me in this build, like before the fix, for the "Reduce/enlarge printout" scale option.

Opened this new bug report, because Mr. Madero doesn't like I had reopened the bug#40788 (comment#56), he reference "experienced developer says don't", developer's comment#53 "The original problem actually is fixed. Tibby reopened it again to move the option to some more intuitive place in the dialogs. However, I suggest to close this bug as fixed (which I do now) and open a new one (which I don't ;-) for the remaining work of getting the option into document specific settings.". What I'm agree, one issue/enhancement one report.
Also I don't see any mention from their side about if he has verified the issue with master build.

I need to learn that fixed bugs are untouchable, because patches don't need verification, and if you dare to do it, and you find it doesn't work, instead reopen, you must report a new one. By the way, we can eliminate the status option verified.

So IMO this should not be marked as duplicate of the bug#40788, it's a regression, except that bug#40788 is reopened again.
Comment 1 Jorendc 2014-05-16 20:28:49 UTC
Okay, quick answer on your whole rant: I do agree with Joel's and Eike's point of view in that bug report. The bug is clearly fixed in 4.2.0, which was then the 'master' version of LibreOffice. And as you state in your comment, you only can reproduce the bug again using LibreOffice 4.3.0. 
So, initial mentioned behavior WAS fixed, and is broken again in 4.3 -> most likely this bug is introduced in another part of the code -> NEW BUG REPORT.

And be fair, that bug report had to be closed eventually. A bug report with +55 comments and was clearly fixed does not invite for a devs-look.
Comment 2 Jorendc 2014-05-16 20:42:08 UTC
@Mario: can you please add some steps to reproduce? I tried with option Tools -> Options -> LibreOffice Calc -> Print -> "Always apply manual breaks" checked and unchecked. Unchecked I create a single page PDF of your sample document. When I enable that option, I export an empty pdf.

Tested using Win 8.1 both 4.2.4 (which should work following your comments), and 4.3.0. 

Kind regards,
Joren
Comment 3 m_a_riosv 2014-05-17 00:42:31 UTC
Hi Joren, thanks for the guide. I forgot to verify the "Always apply manual breaks" option, with so many trials, reset and recovers of the user profile to verify bugs.

I can be agree in report a new bug, in fact I did it, but the only patch there was against master, so perhaps not too much clear, and as you have done, and if I'm not wrong we are trying to avoid duplicates when we can.

Once again please forgive my mistake, but who do nothing don't have mistakes.:)