jtdaugherty/brick
1
1
Fork 0
mirror of https://github.com/jtdaugherty/brick.git synced 2024-09-11 15:55:54 +03:00
Code Issues Projects Releases Wiki Activity

guide: edits

Browse Source
This commit is contained in:
Jonathan Daugherty 2022-12-24 16:33:56 -08:00
parent 0321224a87
commit 4490762640
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/guide.rst
View File

@ -214,8 +214,8 @@ the application state as a result of an event:
appHandleEvent :: BrickEvent n e -> EventM n s ()
``appHandleEvent`` is responsible for deciding how to change the state
based on the event. The single parameter to the event handler is the
event to be handled. Its type variables ``n`` and ``e`` correspond
based on incoming events. The single parameter to the event handler is
the event to be handled. Its type variables ``n`` and ``e`` correspond
to the *resource name type* and *event type* of your application,
respectively, and must match the corresponding types in ``App`` and
``EventM``.
@ -254,11 +254,11 @@ The ``EventM`` monad is a transformer around ``IO`` so I/O is possible
in this monad by using ``liftIO``. Keep in mind, however, that event
handlers should execute as quickly as possible to avoid introducing
screen redraw latency. Consider using background threads to work
asynchronously when it would otherwise cause redraw latency.
asynchronously when handling an event would otherwise cause redraw
latency.
Beyond I/O, ``EventM`` is used to make scrolling requests to the
renderer (see `Viewports`_), obtain named extents (see `Extents`_), and
other duties.
``EventM`` is also used to make scrolling requests to the renderer (see
`Viewports`_), obtain named extents (see `Extents`_), and other duties.
Event Handlers for Component State
**********************************