When queuing calls to the main thread which present speech or braille to the user, ensure they are executed immediately.

[jcsteh]

By default, functions queued with queueHandler.queueFunction are delayed slightly so that queues can implement rate limiting, filter extraneous events, etc. Any of that has already occurred on the server.
Therefore, on the client, we want output to be presented to the user as soon as possible; there's no benefit in delaying further. This should make speech and braille output from the server feel more responsive.

[jcsteh]

There are a couple of other places where self._queueFunctionOnMainThread is called. I didn't change those because it's not clear to me that they need immediate processing and this should only be used where it's necessary for user responsiveness.

[LeonarddeR]

Great to see you contributing here.
Note that I"m currently heavily working on stability improvements, so many things have changed last days. If you would like me to produce a patch in the 1.7.x range, let me know.

[jcsteh]

Oh, I see you just added a few more calls to _queueFunctionOnMainThread. Not sure if you just pushed those commits or if I missed them somewhere. Anyway, I'm not sure whether those need this treatment or not, but I'd tend to lean towards not doing it unless you think it's absolutely necessary. Note that if you queue a non-immediate call and then queue an immediate call, the immediate will override the non-immediate and cause the queue to run immediately.

[LeonarddeR]

I indeed pushed them minutes ago. I got rid of the thread pool executor and addressed nvaccess/nvda#20569