Bug 118481 - Display full view of all conditions in dialogue Conditional formatting for...
Summary: Display full view of all conditions in dialogue Conditional formatting for...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha0+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Conditional-Formatting-Editing
  Show dependency treegraph
 
Reported: 2018-07-01 08:26 UTC by Roman Kuznetsov
Modified: 2020-02-18 02:21 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
Mockup (78.00 KB, image/png)
2018-07-01 08:28 UTC, Roman Kuznetsov
Details
Mockup 2 with checkbox with + and - (85.39 KB, image/png)
2018-07-05 11:02 UTC, Roman Kuznetsov
Details
Mockup 3 with checkbox with + and - (29.19 KB, image/png)
2018-07-05 12:15 UTC, Roman Kuznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Kuznetsov 2018-07-01 08:26:18 UTC
Description:
Display full view of all conditions in dialogue Conditional formatting for... 

Now we show brief view for all conditions except current.

Or make special switcher for this

Steps to Reproduce:
1. Create some conditions for one range in Calc
2. Look at this list.
3.

Actual Results:
Now we show brief view for all conditions except current.

Expected Results:
Display full view of all conditions


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Roman Kuznetsov 2018-07-01 08:28:44 UTC
Created attachment 143247 [details]
Mockup
Comment 2 Heiko Tietze 2018-07-02 06:53:23 UTC
I disagree here, the collapsed sections make sense when many conditions are used. Also, the request without a clear use case like "Benjamin wants to do <Foo> to achieve <Bar>, but is blocked by <Quz>" makes the request sounds like a nice to have for just aesthetical purpose.
Comment 3 Roman Kuznetsov 2018-07-02 09:54:49 UTC
(In reply to Heiko Tietze from comment #2)
> I disagree here, the collapsed sections make sense when many conditions are
> used.

Of course it need when we have several conditions for one range. When I have only one condition, it shows fully always.

> Also, the request without a clear use case like "Benjamin wants to do
> <Foo> to achieve <Bar>, but is blocked by <Quz>" makes the request sounds
> like a nice to have for just aesthetical purpose.

Who is Benjamin?
 
Heiko, did you use conditional formatting yourself? When I have several conditions for one range I have a problem, because I can't see all conditions in one time together. I should remember what's options I set for each condition. And I should switch between conditions to set all conditions right, include ranges of values, colors, sets of icon, styles of cell, etc.

I want offer you discuss it on design meeting.
Comment 4 Heiko Tietze 2018-07-02 16:21:16 UTC
(In reply to kompilainenn from comment #3)
> Who is Benjamin?

https://wiki.documentfoundation.org/Design/HIG_foundations#Persona
  
> ... I can't see all
> conditions in one time together. I should remember what's options I set for
> each condition.

That's a use case. Alternatively to drop expandability we could add information on the collapsed section, introduce user labels, have a summary in tooltips... etc.

> I want offer you discuss it on design meeting.

/added
Comment 5 Cor Nouws 2018-07-04 17:00:03 UTC
(In reply to kompilainenn from comment #3)
> (In reply to Heiko Tietze from comment #2)
> > I disagree here, the collapsed sections make sense when many conditions are
> > used.
> 
> Of course it need when we have several conditions for one range. When I have
> only one condition, it shows fully always.

I like the suggestion for the use case in the mockup. Clearly.
I do not expect that so many conditions are applied on one range, that the expanded views will give less overview of the full list :)

a +1 for me
Comment 6 Heiko Tietze 2018-07-04 19:42:49 UTC
We discussed the topic in the design session. The idea with user-defined strings likely fails due to missing ODF specification. So we recommend to have the section likewise a normal tree (whether plus/minus or triangle to expand/collapse) inclusive an additional expand/collapse all control.
Comment 7 Roman Kuznetsov 2018-07-05 11:02:21 UTC
Created attachment 143316 [details]
Mockup 2 with checkbox with + and -
Comment 8 Roman Kuznetsov 2018-07-05 12:15:25 UTC
Created attachment 143318 [details]
Mockup 3 with checkbox with + and -