https://bugs.documentfoundation.org/show_bug.cgi?id=164337
Patrick (volunteer) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Patrick (volunteer) <[email protected]> --- So here is what I have found so far: SystemWindow::UpdatePositionData() gets called for the floating toolbar immediately after escaping full screen mode. When this is called, the document window has already been moved and resized to its non-full screen size. I can stop the bug from occurring by commenting out Window::ImplCallMove() using the debug patch below. It appears that Window::ImplCallMove() expects all child windows to automatically be pinned to their parent window so when the parent window moves, all of its children move too. Not if this is a problem on Windows or Linux, but on macOS I found that in Window::ImplCallMove() although the parent window had already been moved and resized but the floating toolbar has not. My next step depends on whether or not this bug occurs on Windows or Linux: diff --git a/vcl/source/window/floatwin.cxx b/vcl/source/window/floatwin.cxx index 196f2126cf5b..9ba90632f627 100644 --- a/vcl/source/window/floatwin.cxx +++ b/vcl/source/window/floatwin.cxx @@ -960,7 +960,7 @@ bool SystemWindow::UpdatePositionData() if (pWin) { // Simulate Move, so the relative position of the floating window will be recalculated - pWin->ImplCallMove(); + // pWin->ImplCallMove(); return true; } -- You are receiving this mail because: You are the assignee for the bug.
