<P>
To keep Ion's code as simple as possible yet safe, there are restrictions
when the WObj
-<TT>destroy_obj</TT><A NAME="615"></A>
+<TT>destroy_obj</TT><A NAME="623"></A>
function that calls watches, the deinit routine and frees memory may
-be called directly. In all other cases the <TT>mainloop_defer_destroy</TT><A NAME="616"></A>
+be called directly. In all other cases the <TT>mainloop_defer_destroy</TT><A NAME="624"></A>
function should be used to defer the call of <TT>destroy_obj</TT> until
Ioncore returns to its main event loop.
when the function created a frame to manage some other object but for
some reason failed to reparent the object to this frame.
</LI>
-<LI>In a deferred action handler set with <TT>mainloop_defer_action</TT><A NAME="617"></A>.
+<LI>In a deferred action handler set with <TT>mainloop_defer_action</TT><A NAME="625"></A>.
Like deferred destroys, other deferred actions are called when
Ioncore has returned to the main loop.
</LI>