https://bugs.documentfoundation.org/show_bug.cgi?id=144205
--- Comment #10 from Colin <[email protected]> --- I have further information which appears to be related to the "overall picture" but is directly referencing and comparing performance for "Hide" and "Group and Outline". This bug was identified within "Ask Libre" as pertinent to my enquiry Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded i5 @3.4Ghz 8GB RAM If I open LoCALC and simply set the page format to A4 with all the default margins CALC then produces a marquee defining the print area. If I focus the first cell in row 1 outside the marquee and then select all cells to the right with CTRL+SHFT+RIGHT and then “HIDE” the columns using the context menu, the process is instantaneous. If I then focus the first cell in column A outside the marquee and select all the cells to the bottom and “HIDE” the rows using the context menu, the "HIDE" process takes 4 minutes plus. FOUR MINUTES PLUS - sorry, not shouting, just can't remember how to highlight anymore - Libre Writer does it for me ;)). If I reverse the processes using the toolbar button, the inference is that I’m undoing row height/column width changes and the process is also instantaneous for both UNDOs. However; If I select the columns and >Data>Group and Outline>Group them, then use the activating tab to hide them, the process is still instantaneous. If I select the rows and >Data>Group and Outline>Group them then use the activating tab to hide them, the process is NOW instantaneous. The UNDO button now infers that I’m undoing “Hide details”. My observations/questions: Why is “Hide” claiming to be adjusting the width/height metrics of the column or row, whereas “Group” is claiming to be adjusting the “Hide” characteristics of the related columns/rows? Why is the "HIDE" process far more efficient when operating on columns than when operating on rows? Wouldn’t it be a little more systematic/productive to utilise the same procedures for both operations? -- You are receiving this mail because: You are the assignee for the bug.
