Recursive use of non-recursive std::mtuex in Scheduler::ProcessTaskScheduling?

[Luboš Luňák]

On Tuesday 09 of February 2021, Jan-Marek Glogowski wrote:
> That is the new code from https://gerrit.libreoffice.org/c/core/+/110538
>
> I think we have to revert that. I don't see a way to prevent AnyInput /
> PeekMessage to process messages. There is GetQueueStatus, but I guess
> that's not possible to be used correctly with our complicated user
> WM_USER based setup.

 I think GetQueueStatus() should be sufficient for this specific case. I'll 
try to do that change and see if it helps.

> I wasn't anymore aware, that PeekMessage, called from AnyInput, will
> actually dispatch messages (well - the API docs start with "Dispatches
> incoming sent messages").

 I did notice that, but I thought it was related only to PM_REMOVE. I find 
PeekMessage( PM_NOREMOVE ) processing messages to be pretty lame :(.

-- 
 Luboš Luňák
 l.lunak at collabora.com