From 692e9e3cc401e8c1d71df5e82ba40b193a087023 Mon Sep 17 00:00:00 2001 From: Nitwel Date: Wed, 13 Dec 2023 22:40:08 +0100 Subject: [PATCH] update readme --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 4208d74..a7acafb 100644 --- a/README.md +++ b/README.md @@ -135,6 +135,7 @@ It is also possible to bubble up information by returning a dictionary from a fu | `_on_key_up` | `[event: EventKey]` | The ray-cast leaves the the collision body | | `_on_focus_in` | `[event: EventFocus]` | The node is got focused | | `_on_focus_out` | `[event: EventFocus]` | The node lost focus | +| `_on_notify` | `[event: EventNotify]` | The ui notification system | After considering using the build in godot event system, I've decided that it would be better to use a custom event system. The reason being that we would have to check each tick if the event matches the desired one which seems very inefficient compared to using signals like the browser does.