On Mon, Sep 15, 2008 at 8:33 AM, Hans-Christoph Steiner hans@eds.org wrote:
On Sep 15, 2008, at 3:21 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
Yeah, I thought about that, I shouldn't be too hard, but I am not going to have any time to do it for the next 2 months, probably. Feel free to beat me to it.
Okee - I whipped my first request up today: canvas_name and window_name can now access their parents. I shamelessly copied the code from iemguts : ). Forgot to add credit, will do before I commit. Hans, is it alright if I just commit the changes? I attached the diffs and Intel Mac compiled versions of both if you want to try it out.
I'm going to try to do the subpatch-name version now; do either of you have any tips on how to get the canvas/window from a symbol like "pd-$0.mysubpatch"?
IOhannes, by the way, I compiled iemguts yesterday and wow, what an incredible number of possibilities those objects open up! All of them should be part of vanilla, IMO. Thanks so much for making them - I'll be making a ton of stuff with them in the coming months.
Best Luke
I think that ggee's getdir has a good model for how to do it. Basically, using numbers to represent how many levels down to get from.
this is the scheme i use with the iemguts objects: use numbers to represent how many levels to get _up_.
fmgasdr IOhannes
I think we mean the same thing, just depending on whether it is a tree or roots. ;) If it is a tree, then the parent would be at the bottom.
.hc
All information should be free. - the hacker ethic