[Libreoffice-bugs] [Bug 134684] Conditional Colour Formatting in CALC becomes inconsistent as table columns are deleted

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jul 28 08:52:40 UTC 2021


https://bugs.documentfoundation.org/show_bug.cgi?id=134684

--- Comment #15 from Colin <that.man.colin at gmail.com> ---
CCF = Conditional Colour Format  >Format>Conditional>Colour&Scale

CCF Array = the definition array  >Format>Conditional>Manage

I think it would be prudent for somebody to define precisely what the
convention should be when a CCF protocol has been applied to a CELL a COLUMN or
a ROW that is being copied or inserted or deleted.

It is my perception that the colour formatting should either NOT be propagated
to the modified array with the onus on the user to update the CCF Array or
should duplicate the protocol with a new element in the CCF Array, retaining
the existing criteria but operating intuitively upon the (additional) CCF
array.

1 2 3 4 5 6 7 8 9 10  in array column or row 1 has the indicated minimum and
maximum

4 5 6 7 8 9 10 11 12 13  in array column or row 2 has the indicated minimum and
maximum

at NO time should the presumption be that the global minimum is 1 and the
global maximum is 12 and that 4 5 6 7 8 9 & 10 in both arrays should carry
identical colours. Obviously, I'm referring to the insertion of new array
elements. If the user has defined a two-dimensional array to have an overall
CCF Protocol then we must be able to define/detect this scenario NOT simply
presume it when the array is amended.

Clearly, when a two-dimensional array is being extended by the insertion of new
cells/columns/rows it requires an analysis of the original protocol to define
the likely user anticipation.

Warning the user that changing the boundaries of an array with conditional
formatting requires the user to re-define the conditional formatting places the
onus on the user to remedy the conundrum when changing the structure - The
Simplest Solution (Workaround).

If the array is multiple rows and columns then;

If formatting is detected in a row by row order it is likely the user wishes
the extended boundary to be the limit and the protocol applied over all cells
in the array so, if there are 10 rows/10 columns and a ROW is inserted at row 6
and all columns have their own min & max then each column should have its CCF
Array element adjusted. 10 columnar adjustments which now contain 11 cells.

Likewise, if the formatting is column by column and a new column is inserted
then the user is likely to want the extended columns to be rationalised in the
CCF Array by the extension of each existing CCF protocol.

Now for the trap. If a row is inserted into a columnar priority protocol or a
column is inserted into a row priority protocol then the CCF Array will require
new elements with the appropriate row or column protocol.

It is my experience that insertions and deletions into data arrays supplemented
by a CCF Array are only predictable by their unpredictability.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210728/8c459258/attachment.htm>


More information about the Libreoffice-bugs mailing list