Hans-Christoph Steiner wrote: > So I am just adding support to canvas_name and window_name for > getting the names from other canvases besides the current one, i.e. > parent, toplevel, etc.
OK. > I am using the now standard numeric notation > that is used in [getdir], iemguts, getdollarzero, etc. Care to give a brief description of that for those that don't know? I'd be interested in adding something similar to pdlua, so that .pd_lua(x) files can access the path(s) of their containing patch(es), would make sense to have the same numbers. > What I am wondering is whether it is worth it to add symbol versions > of those names too, like "parent" and "toplevel". this sounds useful at first, but if it's only two cases then maybe it's not worth the hassle... > Or perhaps it > would also be useful to be able to stick the name of a canvas there > too, like 'pd-mysubpatch' or 'pd-canvas_name-help.pd'. Err, why would that be useful if the object is to get the name in the first place (and also, what happens if there are 42 copies of canvas_name-help.pd open...?) > What are > people's thoughts on making that part of the standard technique of > looking up these kinds of things? I think often numbers are nicer than names (eg, I'd hate to have to type "greatgreatgreatgrandparent" instead of 5 or whatever it would be). Claude -- http://claudiusmaximus.goto10.org _______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
