On Thu, 11 May 2023 at 09:54, Stephan Bergmann <sbergman@xxxxxxxxxx> wrote:
Is it plausible that those macro executions trigger asynchronous
operations that might only actually update the values (observed via
rDoc.GetValue) some time after the executeMacro call has already returned?
Given the way our UI works, that is very likely to be the case.
I would suspect that putting a
Scheduler::ProcessEventsToIdle