diff options
| author | ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> | 2023-07-31 19:26:37 +0200 |
|---|---|---|
| committer | ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> | 2023-07-31 19:26:37 +0200 |
| commit | e12eb99b5dc272f0d11eda4be60e5198430b4c4f (patch) | |
| tree | d520d00b82ffdad515e0dfc9248296b247f88dc7 /documentation | |
| parent | 7feddabd24976f90bc950e50c9eb167056359816 (diff) | |
Wayland: add test to avoid null pointer dereferencing
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/src/wayland.dox | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/documentation/src/wayland.dox b/documentation/src/wayland.dox index 04376ce2d..bc94aa1e3 100644 --- a/documentation/src/wayland.dox +++ b/documentation/src/wayland.dox @@ -306,9 +306,10 @@ The \c wl_display_dispatch() call is repeated as long as data are available for The event loop is run by function \c Fl_Unix_System_Driver::wait() which is used by both the Wayland and X11 FLTK backends. Among various tasks, this function waits for data arriving on the file descriptors FLTK is listening. Overall, the event loop of the Wayland backend -is nearly exactly the -same as that used by the X11 backend. The Wayland backend differs only in the callback function -called to handle data read from the Wayland connection socket, which is Wayland-specific. +is nearly exactly the same as that used by the X11 backend. The Wayland backend differs +only in the callback function handling data read from the Wayland connection socket, +and in overridden functions \c Fl_Wayland_Screen_Driver::poll_or_select_with_delay() and +\c Fl_Wayland_Screen_Driver::poll_or_select(). \section wayland-surface Wayland windows and surfaces |