MetzNet
/
dfhack
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

stronger wording for ZScreen guidance

develop
Myk Taylor 2023-01-23 13:46:39 -08:00
parent bf2dcc0070
commit 73dd0b4489
No known key found for this signature in database
GPG Key ID: 8A39CA0FA0C16E78
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/dev/Lua API.rst
Unescape Escape View File

@ -4145,7 +4145,7 @@ ZScreen don't handle the input (i.e. they all return something falsey), the
input is passed directly to the first underlying non-ZScreen. input is passed directly to the first underlying non-ZScreen.
All this behavior is implemented in ``ZScreen:onInput()``, which subclasses All this behavior is implemented in ``ZScreen:onInput()``, which subclasses
should *not* override. Instead, ZScreen subclasses should delegate all input **must not override**. Instead, ZScreen subclasses should delegate all input
processing to subviews. Consider using a `Window class`_ widget as your top processing to subviews. Consider using a `Window class`_ widget as your top
level input processor. level input processor.