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
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
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Would be cool to have exact steps to reproduce. Now I have no idea what I should do.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
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 ...
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.
Dear reversi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I see it resolved in 6.2.
commit 9ea6c0e6777c5b367ec507f10858c9c4be5960ed [log] author Markus Mohrhard <markus.mohrhard@googlemail.com> Thu Jul 26 00:19:06 2018 +0200 committer Markus Mohrhard <markus.mohrhard@googlemail.com> Fri Jul 27 08:01:27 2018 +0200 tdf#109132, load VBA library by default during ODF import Without loading the VBA library any of the functions inside of the library will not be available for spreadsheet functions. *** This bug has been marked as a duplicate of bug 109132 ***