X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;ds=sidebyside;f=ionnotes%2Fnode5.html;h=72551ec12a21d57cb8e6ee38939f7d4aa255950e;hb=ff50b32b3f2fb8bebd445decad84eae135113d0e;hp=45b1c2964cb30faca198b2e78deb86f0465f0e8e;hpb=da1e04def26932e7f91a2106c885142e7fafe59b;p=ion3-doc.git diff --git a/ionnotes/node5.html b/ionnotes/node5.html index 45b1c29..72551ec 100644 --- a/ionnotes/node5.html +++ b/ionnotes/node5.html @@ -28,31 +28,31 @@ original version by: Nikos Drakos, CBLU, University of Leeds
@@ -61,9 +61,9 @@ original version by: Nikos Drakos, CBLU, University of Leeds SubsectionsTo 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 mainloop_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. @@ -102,7 +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. -