[Octave-bug-tracker] [bug #48186] delete(allchild(fig)) in a "deletefcn" callback raises error

[Mike Miller]

Follow-up Comment #7, bug #48186 (project octave):

By the way, there is a comment in the Octave sources dating from 2011 claiming
an intentional order of operations here:

> NOTE: free the handle before removing it from its parent's
>       children, such that the object's state is correct when the
>       deletefcn callback is executed

This seems to imply that the decision was made intentionally to delete the
child object, which calls its deletefcn callback function, before removing it
from the parent's "children" list. So which way is correct?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48186>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/