No subject

you'd get the last object created in the patch, but I didn't try it.

However, canvas_popabstraction does set pd_newest, so you can already use=
=20
pd_newest() if you pretend that the patch is an abstraction.

> About namecanvas, there were two issues that I found when I had a syste=
m=20
> for dynamically loading/unloading and linking together patches that=20
> contained audio: 1) DSP had to be shut off and then turned back on once=
=20
> the linking was done. =A0Sometimes I wouldn't even get audio out of an=20
> object until this happened.

Ah ok, this is not the responsibility of [namecanvas], but I know what yo=
u=20
mean.

> 2) closing a patch that had audio receivers containing $ variables via=20
> the menuclose message was unstable, and would sometimes crash pd. =A0

I don't see how this could ever happen. Is there a way to make a very=20
small patch that causes that crash to happen=A0?

> I didn't ever get to the bottom of these issues, but from what I=20
> understand, [namecanvas] doesn't handle deallocation too well. =A0I los=
t=20
> all this code anyway,

What do you mean you "lost" it ?

> so the new approach I am using for patch maintainence is through libpd=20
> and an object oriented language (objective C at the moment, although I=20
> think I would prefer python for running pd on a laptop/desktop).

So why don't you use libpd's python bindings=A0?

  _______________________________________________________________________
| Mathieu Bouchard ---- t=E9l: +1.514.383.3801 ---- Villeray, Montr=E9al,=
 QC
--751927920-692675677-1300802188=:10342--