Created attachment 184093 [details] examples with no update Watch during debuging Put to the Watch the variable 'level' and debug this macro step-by-step. After the line 'level(0)=p2' it will changed the information in Watch, but after the line 'level=level(0)' it will not change the Watch. Sub dynamArray dim p(2), p2(2), level as variant level=p level(0)=p2 level=level(0) End Sub But if you add the variable 'level' to the Watch after the debugging the line 'level=level(0)', the it is OK. Version: 7.5.0.0.alpha1 (X86_64) / LibreOffice Community Build ID: 2b4d136b65bc79a1248876160e85fab79d52d5d6 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded
Hello, is it only refresh of watch window issue? Because when I do the following steps: Put to the Watch the variable 'level' and debug this macro step-by-step. do not unfold "level" variable in watch window doing debugging to the line 'level=level(0)' unfold "level" variable then it's correct?
Yes, it is correct. The problem is with the refreshing of unfolded variable if the variable is array of array.
I can confirm with Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) and Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 705b2924a14841883b4a8cac549f7af326d7a185 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
Dear Kamil Landa, 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
Bug is still present Version: 25.2.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 5a5fc103cad77dc243b7e54511502054c12c121c CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 17763); UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded