Bug 84745 - EDITING: recalculation issue with user defined function (it is not recalculated)
Summary: EDITING: recalculation issue with user defined function (it is not recalculated)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86 (IA32) All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
 
Reported: 2014-10-07 10:34 UTC by reversi
Modified: 2020-07-07 07:24 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
calc file affected by the descripted error (61.77 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-10-07 10:34 UTC, reversi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description reversi 2014-10-07 10:34:29 UTC
Created attachment 107474 [details]
calc file affected by the descripted error

a user defined function created with basic, named SezReagente(), was recalled in a cell formula as sezreagente(). no way to have it working. after renaming it as SezReagente() it works but every change of input data break again the calculations.
closing and re-opening the file show again the name sezreagente() and the file is not working anymore.

please, check in the attached file the cells: D29 and range from B32 to C37
Comment 1 raal 2014-10-10 19:33:32 UTC
I can reproduce with Version: 4.4.0.0.alpha0+
Build ID: 9aa36a1ad39e37c372cc833a44fba450b8cc30cd
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-10-09_04:46:44
Comment 2 QA Administrators 2015-10-14 19:57:21 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2016-01-29 14:45:49 UTC
Would be cool to have exact steps to reproduce. Now I have no idea what I should do.
Comment 4 QA Administrators 2017-03-06 14:30:53 UTC Comment hidden (obsolete)
Comment 5 b. 2020-07-06 09:30:07 UTC
i'd second @Buovjaga from c#3, 

- but it's a nice return trip if you don't want the users to analyze incomprehensible LO code but annoy the developers with complex macro code ;-)

there are / have been issues with 'capitalism' in naming of functions, 

there are / have been issues with functions not working if in sub modules or other than standard - module1, 

there is an issue with macros / functions not working when called by a button because that 'takes the focus', 

and surely some more ...
Comment 6 b. 2020-07-07 07:24:54 UTC
nearly six years later ... 

funny thing, 

if i'm right in assuming the fault: changing values in B5:E5 should be reflected in app. changes in D29 and B32:E37? 

with LO ver. 6.3.6.1 D29 is shown as '=sezreagente(Rg_Lx;Rg_Ly;Rg_ex;Rg_ey;0;0)' and doesn't calculate but switch to #NAME? on changes in the references / parameters, retyping as 'SezReagente' doesn't help, 

but naming as well the function in Basic editor as the calls in D29 and B32:E37 'SEZREAGENTE()' brings up a - temporarily - working solution, save and reload changes the calls back to 'de-capitalzed' and breaks functionality :-(, thus a capitalism problem? 

with LO ver. 7.1.0.0.a0+ D29 and B32:E37 are auto-shown with 'SEZREAGENTE()' and do! calculate, even by the function name in editor still being 'SezReagente()', 

resolved wfm? could pls. somebody recheck? thanks, 

(does anybody know where the change was?) 

b.