Hello, when I run the following code, the selected cell shows “#NAME?” and its content shows “=dec2hex(A1)” (with lowercases!) dim oSel as object oSel=ThisComponent.currentSelection oSel.Formula="=DEC2HEX(A1)"
I can confirm with Version: 4.3.4.0.0+ Build ID: e812aaaf31050c29a9499d3936cf07079b1a5f86 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time: 2014-11-10_10:51:25 Reproducible with Win7, LO 4.3.3 LibreOffice 3.5.0 Build ID: d6cde02 is oldest version where I can reproduce the problem When I change macro, for example oSel.Formula="=SUM(A1)", then formula is correct.
Reproduced in LibreOffice 3.5.7.2 with Build ID: 350m1(Build:2) and in 4.5.0.0 built from recent master running on Ubuntu 12.04 Occurs also for DEC2OCT and DEC2BIN. Is an issue with all Add-In functions?
Affects Analysis AddIn functions. *** This bug has been marked as a duplicate of bug 78929 ***
Setting back to NEW. Examples from Bug 78929 are solved, bug 78929 is solved -> no Err:508. oSheet.getCellByPosition(2, 0).setFormula("= DEC2HEX(A1)") -> error #NAME?
Hello oligo92, raal, You a
Hello oligo92, raal, Did you try to use DECHEX, function name into LibreOffice, instead of DEC2HEX? The same I think for DECOCT a Regards, Jacques
(In reply to Jacques Guilleron from comment #6) > Did you try to use DECHEX, function name into LibreOffice, instead of > DEC2HEX? Hello, I doesn't see DECHEX in list of available functions. Lo 4.4.0.3
** 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.5 or 5.1.2 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: 2016-04-16
** 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.7 or 5.3.3 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-20170522
This bug it still in v5.3.3.2 Checked on Linux & Windows
version is oldest
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still repro. Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: 37fc9f51a8de11d40632e8cda17ccf1fa4b1f503 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 6 August 2019
in c#3: LeMoyne Castle wrote: "Affects Analysis AddIn functions." in long: looks as if 'add-in' functions as DEC2HEX, DELTA, GESTEP ... are handeled differently to 'built-in'? functions as SUM or AVERAGE, thus a more general problem, i change the title, as manually keying in of 'add-in' functions works, and as setting of cells to plenty other functions (formulas) by a macro works, and as even setting cells to values "3" or strings "text" works from macros, and as even after a 'failed' setting with result "=dec2hex(A1)" a 'nonchanging edit' as 'adding-a-space-and-delete-before-enter' produces a functioning function, i see no reason why setting an 'add-in' function by a macro should fail ... ... but it fails ... anybody an idea why? the string/cell set by the macro must contain some 'special' 'hidden' property??, it can be copied to another cell with result there still 'bad', but if you copy the text from the formula bar into another cell it's capitalized to "=DEC2HEX(A1)" and works as expected, one more funny effect: the unchanging edit 'add-a-space-and-delete-before-enter' works to heal the defects in this case, while other unchanging edits as 'delete-and-undo' or 'replace-and-undo' which helped for some other fails don't help here ??? tests above done with and still repro in: Version: 7.0.0.0.alpha0+ (x64) Build ID: 07b1159b79135857dd9a450c3bb9ae0a944ebcf9 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: reg. b.
This is not a bug. As explained in help [1], all add-in functions (including DEC2HEX) must use a specific syntax (like "com.sun.star.sheet.addin.Analysis.getDec2Hex", not "DEC2HEX"), when passed to setFormula. This is explained in bug 54854 comment 29, and Olivier has improved that help page for version 7.3 to mention the syntax for setting formulas [2]. [1] https://help.libreoffice.org/7.2/en-US/text/sbasic/shared/calc_functions.html?DbPAR=BASIC [2] https://help.libreoffice.org/7.3/en-US/text/sbasic/shared/calc_functions.html?DbPAR=BASIC