The CF manager view in LO Calc has a fixed and much too small horizontal default size, which even cannot be resized manually. Therefore it becomes very cumbersome, i. e. prevents users from working fluently, by quickly getting a wholistic overview, e. g. of a set of longer function-based rules; it forces them, to constantly scroll back and forth between the rule's function and cell range values - so it's next to impossible, to find and edit relevant passages swiftly. It's also not possible to copy-paste these rule functions without clicking 'Edit' first, forcing users to constantly jump back and forth between edit views of single rules and main list. This awkwardness is even greatly amplified by the fact, that the CF manager's main list always jumps to the very end on leaving 'Edit' mode, instead of focusing the last edited rule, which makes checking on and modifying a subset of rules at the beginning or in the middle of a large rule set even more arduous, annoying and time-consuming. Especially for slow machines - e. g. on a Raspberry Pi4 - this process becomes even more tiresome, due to the considerable delays and UI laggyness; a more thoughtful re-design of the CF manager's window features + Copy'n'Paste ability alone could greatly reduce the necessity of repeated and expensive menu context switches. Also, a simple 'Copy' function is tremendously missed, by which users could quickly and intuitively create a larger rule set, without abundant, superfluous (but in Calc mandatory) manual hacking efforts - a very basic, yet vital function, that would certainly at least help mitigate some of CF manager's reported bugs, with minimal effort, like: https://bugs.documentfoundation.org/show_bug.cgi?id=87274 https://bugs.documentfoundation.org/show_bug.cgi?id=165559 https://bugs.documentfoundation.org/show_bug.cgi?id=169201 By giving users back control over CF rule management with an added 'Copy' - and maybe also 'Unite' and 'Split' - function, at least some of the reported problems arising from Calc's unifying and splitting automatic could be mitigated, or made obsolete. https://bugs.documentfoundation.org/show_bug.cgi?id=169206
I suggest leveraging this issue to 'major', to bring an over 10 years old, painful problematic complex to the attention of the dev and designer teams and finally allow for some progress on its behalf.