X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=ionnotes%2Fnode5.html;h=45b1c2964cb30faca198b2e78deb86f0465f0e8e;hb=28274d8cd79bfac0fec675582560463d4b2028f8;hp=51c46f894c67e6f0217feffedb478d18346bab93;hpb=6e84dc8312f2fdb5b8b7467a0279afd5b2df107f;p=ion3-doc.git
diff --git a/ionnotes/node5.html b/ionnotes/node5.html
index 51c46f8..45b1c29 100644
--- a/ionnotes/node5.html
+++ b/ionnotes/node5.html
@@ -83,10 +83,9 @@ original version by: Nikos Drakos, CBLU, University of Leeds
To keep Ion's code as simple as possible yet safe, there are restrictions
when the WObj
-destroy_obj
+destroy_obj
function that calls watches, the deinit routine and frees memory may
-be called directly. In all other cases the
-defer_destroy
+be called directly. In all other cases the mainloop_defer_destroy
function should be used to defer the call of destroy_obj until
Ioncore returns to its main event loop.
@@ -103,8 +102,7 @@ following cases:
when the function created a frame to manage some other object but for
some reason failed to reparent the object to this frame.
-
In a deferred action handler set with
- defer_action.
+In a deferred action handler set with mainloop_defer_action.
Like deferred destroys, other deferred actions are called when
Ioncore has returned to the main loop.
@@ -116,7 +114,7 @@ following cases:
If there are no serious side effects from deferring destroying the
object or you're unsure whether it is safe to destroy the object
-immediately, use defer_destroy.
+immediately, use mainloop_defer_destroy.
@@ -145,7 +143,7 @@ parameters to functions.
| char* |
The string is the caller's responsibility and it
must free it when no longer needed. |
-The called function may modify the string but the ''owner'' of
+ | The called function may modify the string but the ``owner'' of
the string is case-dependant. |