https://bugs.documentfoundation.org/show_bug.cgi?id=167059
--- Comment #30 from Patrick (volunteer) <[email protected]> --- (In reply to Patrick (volunteer) from comment #26) > Is that correct? If yes, there are two things I can do: > > 1. Revert the second block in commit > ad59ecf37f847295e99069281d94518f5afedf90 so that master is essentially the > same as reverting only commit f4c2c7c79cfe4464ac596afda37b8904d06969db i.e. > the timer reschedules itself with POST_PAINT priority. > > 2. Dig through my commits for tdf#163734 and figure out how I ultimately > fixed the docking border drawing. OK. So the first item listed above is now committed on master. So, starting in tomorrow's (09 July 2025) nightly master build, tdf#163734 will likely reoccur. The second item will hopefully fix tdf#163734 but it still needs to be implemented by someone with a Windows machine. Unfortunately, I only have a Mac laptop. I am not familiar with native Windows code but from a quick scan of the code, it looks like the following is the place to copy the macOS flushing code to: diff --git a/vcl/win/window/salframe.cxx b/vcl/win/window/salframe.cxx index 342fffbefe46..9ce3d5d9f3c8 100644 --- a/vcl/win/window/salframe.cxx +++ b/vcl/win/window/salframe.cxx @@ -4278,6 +4278,10 @@ static void ImplCallMoveHdl(HWND hWnd) pFrame->CallCallback(SalEvent::Move, nullptr); +#if HAVE_FEATURE_SKIA + // tdf#163734 Flush parent frame when Skia is enabled +#endif + ImplSalYieldMutexRelease(); } -- You are receiving this mail because: You are the assignee for the bug.
