GNOME Bugzilla – Bug 315853
Distinction between filtered and hidden rows required
Last modified: 2011-04-28 12:18:05 UTC
Version details: ubuntu breezy 1.5.3-2ubuntu2 1. Open a file with data of which I want to paste a subset into a new file. 2. Select the column I want to filter; filter it by a simple criteria. 3. Select All. 4. Copy 5. Paste into a new file Expected result: filtered rows paste in. A quick check confirms that this is what happens in the other open source spreadsheet (openoffice) Actual result: all rows paste in.
*** Bug 317445 has been marked as a duplicate of this bug. ***
I had a quick scan through how this is implemented, and I see it is done by toggling the visibility of a row. The problem with this though is that at least in Excel and OOCalc, the behaviour of rows that are manually hidden is different from rows that are filtered out. EG: in a sheet, selecting rows 4 to 6 and hiding them, then copying a selection A1:A10 copies a 1x10 selection including rows 4, 5 and 6. This works the same in gnumeric, excel and oocalc, so I assume if that behaviour was changed, then that would cause problems for other people. I think it is rather inconistent that rows/columns that the author has chosen to be hidden can be selected, while rows that have filtered out cannot be selected. It looks like rows might need an additional trait to keep track of if they are filtered out or not in addition to their visibility trait.
When a list is filtered, every action on that list should be only applied to visible (filtered) cells/ rows. Example: I have a list of 1000 rows and I filter them through one criterium and get the 200 that I don't need. Gnumeric must allow the user to select all the filtered rows and delete them in one command. As it is, the user has to delete 200 rows, one by one, which is frightning to say the least. This behaviour can also be applied to formatting of filtered cell/rows. This is a MUST have.
*** Bug 343954 has been marked as a duplicate of this bug. ***
*** Bug 358255 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 143220 ***