diff options
| author | Andrea Gelmini <andrea.gelmini@gelma.net> | 2017-09-22 11:23:45 +0200 |
|---|---|---|
| committer | Tamás Zolnai <tamas.zolnai@collabora.com> | 2017-09-22 12:34:13 +0200 |
| commit | ddcdd4a59543fb8e4b6daefe12f3c7e9a8ca0765 (patch) | |
| tree | df1a6e32aecf7af68d371caa57cdd0fc26f77340 /vcl/README.scheduler | |
| parent | 8958240f01b22adebdc4b5b4c79e3cff0d330e3c (diff) | |
Fix typos
Change-Id: I51700733fda3a08570085ed6745961cd1680eabd
Reviewed-on: https://gerrit.libreoffice.org/42588
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Tested-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Diffstat (limited to 'vcl/README.scheduler')
| -rw-r--r-- | vcl/README.scheduler | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/vcl/README.scheduler b/vcl/README.scheduler index 7e80c1f04eb8..deca0d296201 100644 --- a/vcl/README.scheduler +++ b/vcl/README.scheduler @@ -105,7 +105,7 @@ SolarMutex acquire and release calls, so the calling and the main thread don't deadlock. Those wakeup events must be ignored to prevent busy-locks. We can neither rely on MacOS dispatch_sync code block execution nor the -message handling, as both can't be priorized or filtered and the first +message handling, as both can't be prioritized or filtered and the first does also not allow nested execution and is just processed in sequence. There is also a workaround for a problem for pushing tasks to an empty queue, @@ -188,5 +188,5 @@ Instead of LO running in the main process / thread, we run it in a 2nd thread and defer al GUI calls to the main thread. This way it'll hopefully not block and can process system events. -That's just a theory - it definitly needs more analysis before even attemding +That's just a theory - it definitely needs more analysis before even attending an implementation. |