Bug 42286 - FILTER: Auto Filter show blank lines below filtered results
Summary: FILTER: Auto Filter show blank lines below filtered results
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.2 release
Hardware: All All
: medium normal
Assignee: pjacquod
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 09:35 UTC by unconew
Modified: 2011-11-27 10:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The example file (13.14 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-10-26 09:35 UTC, unconew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description unconew 2011-10-26 09:35:13 UTC
Created attachment 52804 [details]
The example file

Problem description: Auto Filter show blank lines below filtered results

Steps to reproduce:
1. Open the file attached
2. Select ADPM in the cell A1
3. What is expected :the filter results are shown with no blank lines below.
   What happens instead : blank lines are shown below the filtered results. As well, these cannot be deleted by pressing the following 3 keys simultaneously:

Ctrl - +

Delete entire row(s) -> OK button

4. turn the filter off and on again, there's one more unwanted line at the bottom !
Comment 1 pjacquod 2011-11-02 14:15:39 UTC
I get the same
I will try to debug sort the point out.
Comment 2 pjacquod 2011-11-06 07:15:56 UTC
Just for the record. 
At initialisation, the parameter nEndRow (a member of ScDBData class) is initialized with a value that does not contain all rows, hence the initial view with some empty rows.

Further, each time the filter is changed, the parameter nEndRow is reduced of 1, which creates the increasing number of empty rows. 

Investigation now in two directions: 
1. why it decreases each time of 1
2. why it initialises not with all rows.
Comment 3 pjacquod 2011-11-27 10:07:16 UTC
solved (with commit 88611e702a18d2 ). This means for users, that this will be solved in 3.5.0 
If the cherry-pick is done to 3.4.5, this version will also have the corrected behaviour. (but still need approbation for 3.4.5)

Best regards