I have tried the software “LibreOffice Calc 6.2.4.2-821.3” (Build-ID: 20(Build:2)) out again. Pivot tables provide also outline functionality. https://help.libreoffice.org/6.2/en-US/text/scalc/guide/datapilot_edittable.html Thus data groups can be folded by a double-click on a table cell. But I got difficulties to notice the folded status of items in the provided (graphical) user interface. I would appreciate clearer indications for the possibility to unfold them again. https://en.wikipedia.org/wiki/Outliner
What exactly do you mean with outline and where do you double click? We have an autofilter, the dropdown on row fields, to quick filter data (besides the filter function mentioned in bug 125857).
(In reply to Heiko Tietze from comment #1) I find that a pivot table can be treated also as an outline editor. https://help.libreoffice.org/6.3/en-GB/text/scalc/guide/datapilot_grouping.html Do the actions vary for a double-click on a table cell of this widget?
Okay, let's talk about the example from this link. Where do you double-click and what exactly do you expect?
(In reply to Heiko Tietze from comment #3) https://help.libreoffice.org/6.3/media/files/scalc/en-GB/pivot.ods 1. A pivot table can be created based on the example data “Car Inventory”. 2. The fields “Branch” and “Car model” can be chosen then for the rows. 3. I suggest to take another look at the software behaviour for a double-click on an entry like “City AA”. Do you see how data are hidden and displayed again? Does this observation fit to the functionality “(un)folding” (for item labels)?
(In reply to Markus Elfring from comment #4) > 3. I suggest to take another look at the software behaviour for a > double-click on an entry like “City AA”. Just to make clear: single click selects a cell like A3 containing "City AA", double-click goes into the edit more. > Do you see how data are hidden and displayed again? > Does this observation fit to the functionality “(un)folding” (for item > labels)? Maybe you have in mind to highlight parts of the chart on selection? I still don't get it.
(In reply to Heiko Tietze from comment #5) > Just to make clear: single click selects a cell like A3 containing "City AA", I agree eventually. > double-click goes into the edit more. I wonder about this wording. I would usually expect an “edit mode” in some cells. > Maybe you have in mind to highlight parts of the chart on selection? Not in this use case. > I still don't get it. Which software behaviour did you see after double-clicking on “branches” in another separate example pivot table?
Looked again into the topic and the workflow is quite common. Single/double click are assigned properly to the interactions and while cross-referencing (selection in charts highlight respective values and vice-versa) sounds interesting it is likely annoying in many situations. Beside the tremendous effort. So WFM.
(In reply to Heiko Tietze from comment #7) > Single/double click are assigned properly to the interactions Yes - to some degree. > and while cross-referencing (selection in charts highlight respective values and vice-versa) sounds interesting Will this aspect be relevant for a separate feature request? > it is likely annoying in many situations. I suggest to reconsider this view once more. Would you occasionally like to recognise a bit easier that specific data were excluded from the display by the pivot table widget?
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
(In reply to Heiko Tietze from comment #7) > Looked again into the topic and the workflow is quite common. Single/double > click are assigned properly to the interactions and while cross-referencing > (selection in charts highlight respective values and vice-versa) sounds > interesting it is likely annoying in many situations. Beside the tremendous > effort. So WFM. Closing as RESOLVED WORKSFORME. For further discussion, please use the UX Team meetings...
(In reply to Xisco Faulí from comment #10) > For further discussion, please use the UX Team meetings... I hope that a nicer user interface experience can still be achieved if the remaining communication difficulties will be resolved somehow.
(In reply to Markus Elfring from comment #11) > (In reply to Xisco Faulí from comment #10) > > For further discussion, please use the UX Team meetings... > > I hope that a nicer user interface experience can still be achieved if the > remaining communication difficulties will be resolved somehow. More UX input needed
(In reply to Xisco Faulí from comment #13) > More UX input needed See comment 7 (I removed the keyword after Markus reopened the ticket).
(In reply to Heiko Tietze from comment #14) * Can it be that you are you still disturbed too much by the cross-referencing idea? * Will a better understanding be achieved for the software behaviour were are usually expecting after double clicks in pivot tables?
(In reply to Markus Elfring from comment #15) > * Can it be that you are you still disturbed too much by the > cross-referencing idea? > * Will a better understanding be achieved for the software behaviour were > are usually expecting after double clicks in pivot tables? Maybe, but you don't need to convince me. We are an open source project where my input is just advice from the UX perspective. And I always try to put the KISS principle first. So uncommon interactions may support your workflow but require most other users to learn it for just one application. But if you find a developer, or do it yourself, your contribution is welcome.
(In reply to Heiko Tietze from comment #16) Can your contribution become a bit more constructive also for this issue?