X-Git-Url: https://git.decadent.org.uk/gitweb/?p=ion3-doc.git;a=blobdiff_plain;f=ionnotes%2Fnode5.html;fp=ionnotes%2Fnode5.html;h=5301a12fe6c60e62fb36ccbbaaf22e6ef06a5f41;hp=72551ec12a21d57cb8e6ee38939f7d4aa255950e;hb=6c79ccf7ddf25af66675865badef0b8f6d0fee78;hpb=ff50b32b3f2fb8bebd445decad84eae135113d0e diff --git a/ionnotes/node5.html b/ionnotes/node5.html index 72551ec..5301a12 100644 --- a/ionnotes/node5.html +++ b/ionnotes/node5.html @@ -83,9 +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 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. -

  • In a deferred action handler set with mainloop_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.