https://bugs.documentfoundation.org/show_bug.cgi?id=54854
--- Comment #22 from Forester <pbronline-freedesk...@yahoo.co.uk> ---
Thanks for the suggestion and apologies for taking so long to look into it.
Is bug 79588 related ?
Using the classic (Aristotelian) model of inquiry we have:
* both have cells showing #NAME!
* both involve add-in functions
* this bug is apparent when first entering an add-in function
* bug 79588 is apparent only when the workbook is re-opened
* this bug, once an add-in function has been entered correctly, #NAME! does
not reappear no matter how many times the workbook is closed and reopened
* this bug concerns add-ins written in Python
* bug 79588 concerns add-in written in Basic
Let's try the pragmatic (Modern) model of inquiry and re-examine what we
already
know about this bug.
1. Not a load issue
See comments 13/14.
Here you are asked to install the add-in and enter two function calls at the
UI. This is successful so I infer any loading of libraries has taken place.
Then you are asked to run a macro that shows the #NAME! problem.
2. Not a Python or a Must-Be-The-User issue
Comment 15 refers to a LibreOffice Basic macro example that shows the problem.
The attachment is not quite as I intended but it is easy to see what was
needed.
Comments 16/17 refer to a Python macro that uses add-in functions that came
with
LibreOffice that shows the #NAME problem. As a wild guess, these add-functions
are not implemented in Python.
This attachment is not at all what I intended. No matter - the functions used
are add-in functions in !LibreOffice 3.5 but not in 5.0 so some productive
tester using 5.0 might have declared "works for me" and closed the bug.
I program Python and perhaps I know a little about how to debug code but when
it
comes to LibreOffice, I am a user of an API. My inquiries have gone as far as
they can without someone who can debug LibreOffice code providing some
assistance.
If one looks at it this way ... comments 13/14:
* enter =functionname(parameters) at the UI gives us what is wanted
* use a macro to enter = unoComponentId.functionname(parameters) likewise
* use a macro to enter =functionname(parameters) gives #NAME!
* enter = unoComponentId.functionname(parameters) at UI gives #NAME! too
Notice the inconsistency ?
I disassembled a workbook and found that, internally, LibreOffice stores
= unoComponentId.functionname(parameters).
It seems LibreOffice can do the conversion but doesn't when using a macro to do
data entry. It seems like the code exists but just isn't being called on this
particular execution path. Hypothesis: Frame-Controller-Model.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
