[Libreoffice-bugs] [Bug 66717] Allow use scalar User-defined Functions with range arguments, similar to built-in functions

[bugzilla-daemon at bugs.documentfoundation.org]

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

Wolfgang Jäger <jag at psilosoph.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jag at psilosoph.de

--- Comment #14 from Wolfgang Jäger <jag at psilosoph.de> ---
Created attachment 144449
  --> https://bugs.documentfoundation.org/attachment.cgi?id=144449&action=edit
Demonstration of elaborate workarounds covering the mixed case

(In reply to Mike Kaganski from comment #13)
> ...
> As I mentioned above, using 0+range doesn't work for mixed number/string
> case.

I doubt if designing sheets for "mixed number/string cases" is good practice at
all. 

Anyway you can enhance the mentioned workaround by 
=FUNC(IFERROR(0+range;"" & range))
which should work in most cases though sometimes automatic conversions may
interfere. A more elaborate, but overtorqued(?) example you find in the new
attachment. It also demonstrates the workaround 
=FUNC(INDEX(range;ROW()-ROW(range)+1)) 
which also comes with some disadvantages, of course.

However, 
I would expect this old enhancement-bug to be classified "wontfix" some day. 
As I see it the intersection-mode is of use only in connection with named
ranges. To omit one or a few ranges -or to only reference them in specific
formulae- for getting rid of the problem should be an acceptable workaround not
relying on long formulae like in the new example.
Anyway named ranges aggravate scaling, and enhancement of sheets sometimes. 
(Excel enthusiasts on YouTube may bias users to apply named ranges,.. Are there
interoperability issues?)

-- 
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/20180826/19d412be/attachment.html>