Bug 37259 - FORMATTING Define Print Range across filtered rows fails
Summary: FORMATTING Define Print Range across filtered rows fails
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Spreadsheet (show other bugs)
Version: 3.3.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-16 08:04 UTC by Jaap Stolk
Modified: 2015-01-20 14:40 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
spreadsheet file with an auto filter, hiding several rows (12.89 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-05-16 08:04 UTC, Jaap Stolk
Details

Description Jaap Stolk 2011-05-16 08:04:33 UTC
Created attachment 46771 [details]
spreadsheet file with an auto filter, hiding several rows

Rows in a LibreOffice Calc sheet can be hidden using a data filter.

What does not work:

Defining a Print Range using a selection across any of the hidden rows fails (without error message).

What does work:

Defining the Print Range using a selection when the filter shows "All" data. (no hidden rows)
Defining the Print Range across hidden rows, using "Format"-> "Print Ranges" -> "Edit" -> "-User Defined-" -> "$A$13:$D$25".
Defining the Print Range using a selection, somewhere that does not cross any hidden rows.
After successfully setting the Print Range, the filter can then hide rows, and these hidden rows are not printed (as expected).

What has no effect:

If the section is made using the keyboard with "Shift", has the same problem as when the selection is made using by dragging the mouse.
(When selecting the range with the keyboard, the down button also cycles through the hidden rows)
"Normal" or "Page break view" makes no difference, just easyer to see that setting the Print Range failed.

Expected behaviour:

Defining a Print Range using a selection across hidden(filtered) rows should work, just like entering the Print Range cell numbers manually in the Edit Print Range window.

The attached filtered_print_range.ods is created from scratch in (Win32) LibreOffice 3.3.2, and has only been saved in the native ods format.

found in:
LibreOffice 3.3.2 OOO330m19 (Build:202) tag libreoffice-3.3.2.2 (Windows XP) (Dutch, 32-bit)

confirmed in:
LibreOffice 3.3.2 OOO330m19 (Build:202) tag libreoffice-3.3.2.2, Ubuntu package 1:3.3.2-1ubuntu4 (English, 32-bit)
Comment 1 Jaap Stolk 2011-05-16 08:31:14 UTC
Confirmed in latest beta:
LibreOffice 3.4.0 DEV300m103 (Build:5) Windows XP 32-bit
Comment 2 Björn Michaelsen 2011-12-23 12:04:57 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 Florian Reisinger 2012-08-14 13:59:01 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 14:00:14 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:04:55 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:07:01 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 sasha.libreoffice 2012-09-05 07:45:12 UTC
Works in 3.6.1 on Fedora 64 bit
used this: Format->Print range->Edit
for assigning print range for selection
so, WFM
Comment 8 Jaap Stolk 2012-09-05 08:53:59 UTC
Format->Print range->Edit works (as I stated in the original report), even choosing the "use selection" option in that dialogue works (which I did not try before).
But the reported problem: setting the print range using Format->Print range->Define (crossing hidden rows of an autofilter) is still there.

I just confirmed this bug in version 3.6.1.2 e29a214 (Windows 32-bit)

Regarding Bugzilla: this report was automatically changed from NEW to NEEDINFO,
and then automatically closed after 6 month, without anyone actually asking for more info. Since I'm the original reporter, I'm not sure whether that counts as VERIFIED, so I'm changing it to REOPENED.
Comment 9 Florian Reisinger 2012-09-05 09:23:00 UTC
Yep, confirming this bug @ Windows 7 x64 LibreOffice 3.6.2.1
Comment 10 QA Administrators 2015-01-05 17:51:55 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
Comment 11 Beluga 2015-01-20 14:40:10 UTC
Still reproducible.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 07e84cae983c08afdba03018413a19d01abb3006
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.