Re: defer_front – can I rely on this regarding this context?


Forums > Dev > defer_front – can I rely on this regarding this context?
January 3, 2013 | 11:04 am

Hey Nicolas, thanks for helping

in practice using defer_front has the effect that
itm_dereference(x->track_itm);
is called before the referenced transport is deleted.
Calling itm_dereference without defer_front does somehow not work in my case.

If the transport is not dereferenced properly I’m experiencing
artefacts the next time I create a transport with the same name.

About your idea: are you sure the object receives the notification before it’s free method is called?
And aren’t notifications then send for any action regarding the patcher?