suzanne.soy/gui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc correction

Browse Source 
Closes PR 11465

original commit: 430d45b471aff9d3b09f21ed11aedae1b4067396
This commit is contained in:
Matthew Flatt 2010-11-27 08:28:57 -07:00
parent 657512f567
commit cde87458e6
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
collects/scribblings/gui/editor-overview.scrbl
View File

@ -720,11 +720,10 @@ An editor is not tied to any particular thread or eventspace, except
to the degree that it is displayed in a canvas (which has an to the degree that it is displayed in a canvas (which has an
eventspace). Concurrent access of an editor is always safe, in the eventspace). Concurrent access of an editor is always safe, in the
sense that the editor will not become corrupted. However, because sense that the editor will not become corrupted. However, because
editor access can trigger locks, and because lock-rejected operations editor access can trigger locks, concurrent access can produce
tend to fail silently, concurrent access can produce unexpected contract failures or unexpected results.
results.
Nevertheless, the editor supports certain concurrent patterns An editor supports certain concurrent patterns
reliably. One relevant pattern is updating an editor in one thread reliably. One relevant pattern is updating an editor in one thread
while the editor is displayed in a canvas that is managed by a while the editor is displayed in a canvas that is managed by a
different (handler) thread. To ensure that canvas refreshes are not different (handler) thread. To ensure that canvas refreshes are not