Description: CALC Document: Size/Position of Push Buttons is modified after Open/Save/Close of CALC Document for many times. Steps to Reproduce: See attached file Steps_To_Reproduce_And_Results.ods ! Actual Results: Size/Pos of Push Buttons is modified. Expected Results: Size/Pos of Push Buttons should not be modified. Reproducible: Always User Profile Reset: No Additional Info: Tested using LO 6.4.5.2 (x64) @ Windows 10 Home
Created attachment 163591 [details] Steps_To_Reproduce_And_Results.ods
Created attachment 163592 [details] CALC.ods
Created attachment 163593 [details] CALC.bas
Some more clearness: [1] Software used: LO 7.0.0.3 (x64) @ Windows 10 Home (x64). [2] The 'original files': + LO7testA1.ods + LO7testB1.ods + LO7testC1.ods + LO7testD1.ods For all files: + Opened new CALC document (Untitled 1.ods). + Inserted 9 push buttons: ++ Test A: Cells A1 to A9 ++ Test B: Cells B1 to B9 ++ Test C: Cells A2 to A10 ++ Test D: Cells B2 to B10 + For every push button: ++ [Anchor] > [To cell (resize with cell)] ++ [Control Properties] > [General] > [Label] Modified: "Puh Button" to "Push Button 'numbering'" + For the sheet "Sheet1": ++ All rows: [Optimal Height] ++ All columns: [Optimal width] + Saved/closed [3] The macro used for testing: LO7testCALC.bas [4] The 'modified files' (copies of 'original files') processed by macro: + LO7testA2.ods + LO7testB2.ods + LO7testC2.ods + LO7testD2.ods [5] The summary: LO7testResults.ods Size/Pos of some push buttons is modified after 100 open/save/close cycles. There seems to be a very small difference of 0,002 cm added on by 100 cycles to the 0,2 cm difference as to be seen. Why happens this adding on ? [6] All files attached.
Created attachment 163849 [details] LO7testResults.ods
Created attachment 163850 [details] LO7testMacro.bas
Created attachment 163851 [details] LO7testA1.ods
Created attachment 163853 [details] LO7testA2.ods
Created attachment 163854 [details] LO7testB1.ods
Created attachment 163855 [details] LO7testB2.ods
Created attachment 163856 [details] LO7testC1.ods
Created attachment 163857 [details] LO7testC2.ods
Created attachment 163858 [details] LO7testD1.ods
Created attachment 163859 [details] LO7testD2.ods
Created attachment 163864 [details] modified macro toto show the heights of push button 1 for all cycles I can confirm the bug. Not all four files need to be tested, the behaviour is seen already in LO7testD2, the only test I made. I modified the macro to record the height of push button 1 in every cycle. The array containing these values is shown at the end of the macro, I used Xray to present it, it's easier than programming a loop. The result is shown in the attachment LO7TestHeights.txt, the height diminishes slowly, every 13 or 14 cycles the value is 1 lees than before. So running for 100 cycles is perhaps helpful for the optical control, but not necessary for showing the effect via program, the height is already diminished after less than ten cycles. I also tested with a reduced file where I had deleted push buttons 2 to 9, the result for the height of push button 1 is nearly the same, some changes from one value to the next happen one step earlier or later.
Created attachment 163865 [details] Result of a run with macro LO7testMacro_mod
Created attachment 163869 [details] Test_1_Results_LO7vsLO3.ods
Created attachment 163870 [details] LO3testB1_test_1_file_created_by_LO7.ods
Created attachment 163871 [details] LO3testB2_test_1_file_created_by_LO7.ods
Created attachment 163872 [details] Test_2_Results_LO3.ods
Created attachment 163873 [details] LO3testB1_test_2_file_created_by_LO3.ods
Created attachment 163874 [details] LO3testB2_test_2_file_created_by_LO3.ods
Some more tests using LO 3.6.7.2 (32x) @ Windows Home (x64) ... Macro used: LO7testMacro.bas [1] Test 1 + Files used: ++ LO3testB1_test_1_file_created_by_LO7.ods ++ LO3testB2_test_1_file_created_by_LO7.ods (copy of file above) + Test results: ++ File: Test_1_Results_LO7vsLO3.ods ++ The difference is only 50% checked against LO7-Tests. ++ Push buttons affected: +++ LO7: ++++ Pos X and Width: all ++++ Pos Y and Height: 2,4,6,8 +++ LO3: ++++ Pos X and Width: all ++++ Pos Y and Height: 3,5,6,8 [2] Test 2 + Files used: ++ LO3testB1_test_2_file_created_by_LO3.ods ++ LO3testB2_test_2_file_created_by_LO3.ods (copy of file above) + Test results: ++ File: Test_2_Results_LO3.ods ++ The difference ist 0% !
S U M M A R I Z E [1] LO 7.0.0.3 (x64) @ Windows 10 Home (x64) When a CALC document is opened/saved/closed for 15 times or more, the parameters (Pos X,Pos Y,Width,Height) of some push buttons, placed in the CALC document, are modified by LibreOffice without any additional user interaction. See: LO7testResults.ods See: Result of a run with macro LO7testMacro Mod (= LO7TestHeights.txt @ Comment 15) [2] LO 3.6.7.2 (32x) @ Windows Home (x64) No modifications to be seen. See: Test_2_Results_LO3.ods. [3] For testing: Use: LO7testMacro.bas Use: modified macro toto show the heights of push button 1 for all cycles [4] For details see the other attched files.
Sorry, ED forgotten, meant S U M M A R I Z E D ...
Dear Hans-Werner, 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
Created attachment 181598 [details] TestMacro.bas
Created attachment 181599 [details] LO 7.4.0.2 -1- CalcOrg.ods
Created attachment 181600 [details] LO 7.4.0.2 -2- CalcMod.ods
Created attachment 181601 [details] LO 7.0.0.3 -1- CalcOrg.ods
Created attachment 181602 [details] LO 7.0.0.3 -2- CalcMod.ods
R E S O L V E D TestMacro.bas New Test - OKAY LO 7.4.0.2 -2- CalcOrg.ods <EQUAL> LO 7.4.0.2 -2- CalcMod.ods Old Test - ERROR LO 7.0.0.3 -1- CalcOrg.ods <NOT EQUAL> LO 7.0.0.3 -2- CalcMod.ods