https://bugs.documentfoundation.org/show_bug.cgi?id=111675
--- Comment #19 from Mike Kaganski <[email protected]> --- (In reply to Andreas Heinisch from comment #18) > The problem here ist that the calculations within the IFS function (for > instance the DIV) are evaluated before the actual IFS function itself. > Hence, any further calculation leads to a DIV to ZERO error, because if > there is an error, no further calculations are made. I do not see this to be *directly* related to the original problem: (In reply to Michael from comment #9) > If you look on my example attached > (https://bugs.documentfoundation.org/attachment.cgi?id=135441), the IFS > formula in B5 is: > > =B2+STYLE(IFS(CURRENT()<B3;"Grün";CURRENT()=B3;"Gelb";CURRENT()>B3;"Rot")) Additionally, I do not see how could "IFS() and SWITCH() should short-cut evaluation like IF() and CHOOSE()" title (change by Eike from 2018-03-12) be directly related here for the initially stated problem ("UI: Functions IFS does not work together with function CURRENT"). While it might be reasonable to add short-circuiting to the IFS and SWITCH, I do not see how that could avoid evaluating the "unneeded" branches in the presence of CURRENT (or, more specifically, how could it avoid changing CURRENT value "unexpectedly"), which necessarily evaluates what was put to stack last before this invocation of CURRENT, and thus must take either the next or the previous *Value N* argument value - whichever direction the evaluation uses, but definitely not what user would naively expect (that it would use something from the distant past in the formula), independent of the short-circuiting that CHOOSE might do. -- You are receiving this mail because: You are the assignee for the bug.
