@AnttiK
Do you mean:
qGuiApp->processEvents(QEventLoop::ExcludeUserInputEvents);
The documentation says, that the use of this function is discouraged, that's actually what made me do it the other way.
I also tried:
this->thread()->eventDispatcher()->processEvents(QEventLoop::ExcludeUserInputEvents);
They all seem to work similar.
The event get processed, i don't think, this is the problem.
I guess, the problem is, that the event is not in the event queue when i want to process them.
Initially, i assumed, that the event for rerendering get pushed to the queue as soon as the qml scene changes.
But it's not even after QWindow::requestUpdate() present, i have to wait an unspecific amount of time, which feels very wrong to me...
Thank you for your timeout suggestion.
Yes, i will use something like that to definitely avoid any deadlocks.
If i'll actually use my approach in the end...
After all, i wonder, how others deal with this very common situation.
Because you NEED to do something similar in such a start-up routine.
The docs of QEventLoop::processEvents even give the hint to use it in this situation.
Maybe it's just a bug, did you test forceUpdateSimple()?
Thank you very much!