Created attachment 64805 [details] Excel test file with macro The Excel Visual Basic code "Application.ScreenUpdating = False" does not work or will be ignored. Because this code will be ignored it is not possible to disable the updating of the screen and some macros are working very slow in LibreOffice! Try to run the example macro in Excel and compare it with LibreOffice Calc. Example macro: Sub Test_ScreenUpdating() ' Testing Excel VBA Code in Libre Office: Range("A4").Select Application.ScreenUpdating = False For i = 1 To 10000 ActiveCell.Offset(1, 0).Select Next i Range("A4").Select Application.ScreenUpdating = True End Sub
This bug occurs in LibreOffice version 3.5.6 and 3.6.1 also
On pc Debian x86-64 with master sources updated yesterday, I can reproduce this. Noel: I checked on Opengrok, a setScreenUpdating method exists but is never called, see: http://opengrok.libreoffice.org/search?q=setScreenUpdating&project=core&defs=&refs=&path=&hist= See also: http://opengrok.libreoffice.org/search?q=ScreenUpdating&project=core&defs=&refs=&path=&hist= Are we near the goal with all this?
This bug was also reproduced in newer versions of LibreOffice for Windows! Tested with LibreOffice versions: 4.0.4.2, 4.1.4.2 and 4.2.0.4 Moreover to that the last version of LibreOffice 4.2.0.4 shows a significant performance degradation to scroll down through cells via macro!!! Needed time to scroll down through 10000 cells: LibreOffice 4.0.4.2: 00:15 [mm:ss] LibreOffice 4.1.4.2: 00:15 [mm:ss] LibreOffice 4.2.0.4: 01:38 [mm:ss] (!!!) Needed time with Excel to compare: Excel 2010 with "Application.ScreenUpdating = False": ~00:01 [mm:ss] Excel 2010 with "Application.ScreenUpdating = True" : 00:05 [mm:ss] (Test system: Windows 7 64-bit, Intel Core2Duo P8700 2.53 Ghz, 4 GB RAM, Java SE Runtime Environment build 1.6.0_24-b07) Could anybody reproduce the bug and the performance degradation in LibreOffice 4.2.0?
This bug was reproduced also in LibreOffice Calc version 4.2.3.3 and 4.2.4.1 rc!
** 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 (4.4.3 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-06-08
The problem still exists! This bug was also reproduced in LibreOffice 4.4.3.2!
I searched a bit and all the mechanism for this seems to be there, here's a bt when I'm on "ScreenUpdating=false" (gdb) bt #0 0x00002aaaca2c5ae1 in ScModelObj::lockControllers() (this=0x29c1920) at /home/julien/compile-libreoffice/libreoffice/sc/source/ui/unoobj/docuno.cxx:1652 #1 0x00002aaaae1d86c7 in basic::vba::(anonymous namespace)::lclLockControllers(com::sun::star::uno::Reference<com::sun::star::frame::XModel> const&, bool) (rxModel=uno::Reference to (ScModelObj *) 0x29c19b0, bLockControllers=true) at /home/julien/compile-libreoffice/libreoffice/basic/source/basmgr/vbahelper.cxx:110 #2 0x00002aaaae1d8b05 in basic::vba::(anonymous namespace)::lclIterateDocuments(basic::vba::(anonymous namespace)::ModifyDocumentFunc, com::sun::star::uno::Reference<com::sun::star::frame::XModel> const&, bool) (pModifyDocumentFunc=0x2aaaae1d8685 <basic::vba::(anonymous namespace)::lclLockControllers(com::sun::star::uno::Reference<com::sun::star::frame::XModel> const&, bool)>, rxModel=uno::Reference to (ScModelObj *) 0x29c19b0, bModificator=true) at /home/julien/compile-libreoffice/libreoffice/basic/source/basmgr/vbahelper.cxx:164 #3 0x00002aaaae1d8c18 in basic::vba::lockControllersOfAllDocuments(com::sun::star::uno::Reference<com::sun::star::frame::XModel> const&, bool) (rxModel=uno::Reference to (ScModelObj *) 0x29c19b0, bLockControllers=true) at /home/julien/compile-libreoffice/libreoffice/basic/source/basmgr/vbahelper.cxx:187 #4 0x00002aaacfaf5f15 in VbaApplicationBase::setScreenUpdating(unsigned char) (this=0x2e79030, bUpdate=0 '\000') at /home/julien/compile-libreoffice/libreoffice/vbahelper/source/vbahelper/vbaapplicationbase.cxx:193 Eike: any idea why the document view locking mechanism doesn't work here?
This problem still exists and was reproduced in LibreOffice versions 4.4.7.2, 5.0.4.2, 5.1.1.3 and 5.1.4.2 for Windows. (Test system: Windows 7 64-bit, Intel Core2Duo P8700 2.53 Ghz, 4 GB RAM, Java SE Runtime Environment build 1.6.0_24-b07)
Changing version back to the earliest affected version.
Bug also reproduced with LibreOffice version 5.4.2 (Version 5.4.2.2 for Windows)
Dear Tor24_1975314, 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
Bug also reproduced with LibreOffice Version 6.3.3.2 (x64) for Windows. W10 platform. Tested using Calc. lockControllers / unlockControllers doesn't function either and may be related. It would be really useful to get this fixed for performance reasons.
*** Bug 149559 has been marked as a duplicate of this bug. ***
The ScreenUpdating.xls Excel spreadsheet [attachment](https://bugs.documentfoundation.org/attachment.cgi?id=180744) at bug 149559 has two functions, whereby "Application.ScreenUpdating = False" fails and the other that works. They can be found by: 1. Macro Selector 2. Library: ScreenUpdating.xls → VBAProject → ThisWorkbook 3. Macro Name: Either "ScreenUpdateTestFails" or "ScreenUpdateTestWorks" Tested with: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: ca47989ad60b1414f92be22a1fbf4c1d1a92dd97 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded using Linux Mint 20.3 Cinnamon. Does the testcase help solve this issue? Thank you
"Excel test file with macro" bug also reproduced with LibreOffice: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: ca47989ad60b1414f92be22a1fbf4c1d1a92dd97 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded with Linux Mint 20.3 Cinnamon. Thank you
Dear Tor24_1975314, 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