Description: Good day to you. AutoFit method does not work if Application.ScreenUpdating set to False. Tested on 6.3, 7.5, 24.2, and 25.2.4.3. You can just set some long enough string to Cell "A1" and check it. ```basic Option VBASupport 1 Public Sub VBAMain() Application.ScreenUpdating = False Rows(1).AutoFit Application.ScreenUpdating = True End Sub ``` Moreover, if I forget to set Application.ScreenUpdating to True then I'm not able to autofit even using interface, double-clicking on a bottom border of a row. Actual Results: No results Expected Results: Actual row height autofit Reproducible: Always User Profile Reset: No Additional Info: It's either I don't know how to write it correctly in LibreOffice Basic, or ThisComponent.LockController works perfectly.
Testing this in 26.2 and later is affected by bug 169110. It causes this: BASIC runtime error. '423' Property or method not found: ScreenUpdating. I reproduce the main issue already in oldest of Windows 4.3 bibisect repo.
This looks interesting since this bug was filed before the Object Browser work was merged, yet it now follows the same failure path as the VBAGlobals/CutCopyMode regression. The raw-source reading solution is relevant for bug 169110. However, the `Application.ScreenUpdating = False`/ `AutoFit` behavior here likely represents a separate issue in the Calc VBA implementation rather than being caused by the Object Browser regression.
(In reply to Devansh Varshney from comment #2) > This looks interesting since this bug was filed before the Object Browser > work was merged, yet it now follows the same failure path as the > VBAGlobals/CutCopyMode regression. > > The raw-source reading solution is relevant for bug 169110. > > However, the `Application.ScreenUpdating = False`/ `AutoFit` behavior here > likely represents a separate issue in the Calc VBA implementation rather > than being caused by the Object Browser regression. Sure, my comment in this report was just a heads up, so others don't wonder.