Description: After you install the new LO6.3 my DB was paralyzed shimmering buttons. In 6.2 everything worked normally. In my database I use the built-in calc object in which I form a lot of control buttons using macros. These buttons are constantly drawn, tremble and strongly inhibit the work of all databases. Steps to Reproduce: 1. Download and unpack the attached archive 2. Import macros as described in the Readme 3. Start the database and in the opened form start any of the dark gray buttons, especially the 5th or 6th Actual Results: The table in the nested calc-table will be formed in which the problem buttons will also be formed Expected Results: Buttons should not shake and constantly draw, be stable. The table should be formed quickly. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
Created attachment 154616 [details] Database Database with built-in forms calc-tables
The steps from the "ReadMe.txt", with modifications: 1. Unpack the downloaded DB.zip from attachment 154616 [details] 2. Open LibreOffice (*don't* open the DB yet), go to Tools->Macros->Organize Macros->LibreOffice Basic 3. Click "Organizer..." button 4. Open "Libraries" tab; click "Import" 5. Navigate to "DBLibrary" subdirectory in the place where the DB.zip was unpacked to; select "dialog.xlb" anc click "Open" 6. Confirm (no need to check "Replace existing libraries" yet) 7. Repeat 4-6, choosing "script.xlb" instead of "dialog.xlb" this time, and checking "Replace existing libraries" 8. Repeat 4-6, navigating to "Library1" instead of "DBLibrary" this time 9. Repeat 4-6, navigating to "Library1" instead of "DBLibrary" this time, choosing "script.xlb" instead of "dialog.xlb", and checking "Replace existing libraries" (A comment: the steps 4-9 seem strange; no idea why is the repeated import which replaces a library imported in the previous step is needed) 10. In the same "LibreOffice Basic Macro Organizer" dialog, switch to "Modules" tab 11. Drag "DBConnect", "dlgALL", and "iListener" from "Library1" to "Standard" 12. Open the DB.odb from the unpacked archive. Confirm enabling macros. A form should automatically open. No errors should occur at this stage 13. If the form shown an empty Calc-like grid with column/row labels, click inside the grid, and it should become blank without column/row headers (I needed to do that click; no idea if there's some circumstances where the blank area would appear from the beginning) 14. Click on one of the buttons inside "ЗАКАЗЫ" category in the top right part of the form: either "ПРОФЛИСТ" or "МЕТАЛЛ". In my testing, both with Russian UI and with en-US UI, with or without relevant help pack installed (which is mentioned for some reason in English part of the ReadMe.txt), I see slow population of the list. I could see no flickering; but the drop-down menus in the program became blank (but clickable); opening Help->About (guessing its position in menu by memory) opened the dialog, which was *also blank*. Tested with Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded More information is needed: what specifically is wrong in the process. If possible, a screen cast would be nice, with problematic parts marked or commented in a description (like "at 3:15, left bottom corner, button "XXX" flickers"); also if this is a regression, and full information from Help->About.
this issue could be a duplicate of: Bug 121963 - button flashing - mouse wheel zooming breaks
(In reply to Mike Kaganski from comment #2) > In my testing, both with Russian UI and with en-US UI, with or without > relevant help pack installed (which is mentioned for some reason in English > part of the ReadMe.txt), I see slow population of the list. I could see no > flickering; but the drop-down menus in the program became blank (but > clickable); opening Help->About (guessing its position in menu by memory) > opened the dialog, which was *also blank*. > > Tested with Version: 6.3.2.2 (x64) > Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c > CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; > Locale: ru-RU (ru_RU); UI-Language: en-US > Calc: threaded > @Mike, since your testing with OpenGL showed some controls drawn blank, do you get similar with OpenGL rendering disabled and using default GDI rendering? Or do you get a flicker? I ask because some of the renderContext GUI issues that flicker for sure--draw blank GUI elements (for a moment and that then render fully). Should this go into the Meta bug 91488
Created attachment 154631 [details] screenshot Added a screenshot highlighting the problem area
Created attachment 154632 [details] Video (7.5MB) Added a screen-video with the problem
Enabling or disabling OpenGL has no effect on the problem.
(In reply to Oliver Brinzing from comment #3) > this issue could be a duplicate of: > > Bug 121963 - button flashing - mouse wheel zooming breaks Quite possible. Mouse flickering is also observed. My testing showed that the problem appeared after the next commit: d0bdd6cb45a812e383d6efb91012d597aae5f116 is the first bad commit commit d0bdd6cb45a812e383d6efb91012d597aae5f116 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Fri Nov 30 13:41:59 2018 -0800 source d464d505fbf6e53a38afdd3661d320fac8c760d6 source d464d505fbf6e53a38afdd3661d320fac8c760d6 :040000 040000 bf285e1cfb3224de3584a8c6aed6f3a5da0fd997 fa8381282f278eb33ba9036548fae09cbe9a0d76 M instdir
Created attachment 154636 [details] Video2 Added another video with increased visibility of problems because they report that they can not see the problem.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Kadet from comment #8) > (In reply to Oliver Brinzing from comment #3) > > this issue could be a duplicate of: > > > > Bug 121963 - button flashing - mouse wheel zooming breaks > > > Quite possible. Mouse flickering is also observed. My testing showed that > the problem appeared after the next commit: > > d0bdd6cb45a812e383d6efb91012d597aae5f116 is the first bad commit > commit d0bdd6cb45a812e383d6efb91012d597aae5f116 > Author: Norbert Thiebaud <nthiebaud@gmail.com> > Date: Fri Nov 30 13:41:59 2018 -0800 > > source d464d505fbf6e53a38afdd3661d320fac8c760d6 > > source d464d505fbf6e53a38afdd3661d320fac8c760d6 > > :040000 040000 bf285e1cfb3224de3584a8c6aed6f3a5da0fd997 > fa8381282f278eb33ba9036548fae09cbe9a0d76 M instdir Thanks for the bisection. It does confirm it's a duplicate of bug 121963 *** This bug has been marked as a duplicate of bug 121963 ***
Apparently indeed, a duplicate of bug 121963 But I will continue here. Further research has shown that the same error prone checkboxes. And perhaps other controls (not tested). It was also found that the error is an offset error. If you bind the buttons to the cell 0-th or 1-th column with an offset of 0, the flicker is not observed. Already with column 2 there is flickering. And the farther away from the 0-th column of the flickering activity. Also doesn't help if the snap button to the cell of the 0-th column and the offset. There is no shift and the button is at the 0-th position, but there is a strong flicker, even at the 0-th position.
Created attachment 155108 [details] Shift buttons down the Y-axis. Added a screenshot. When you create a table, the macro creates buttons that are bound to row cells. If there are many rows and rows of different heights, the bound buttons are shifted down the Y-axis.