It's in m_pd.h - that's a pretty good guarantee of stability (although not 100% perfect I'm afraid.)
One caution -- if soneone 'saves' the patch into a new directory, the canvas's directory will then change -- so it's best not to store the result of canvas_settid() but to call it each time it gets used.
cheers Miller
On Wed, Jul 13, 2011 at 01:46:06PM -0700, Jonathan Wilkes wrote:
--- On Wed, 7/13/11, IOhannes m zmoelnig zmoelnig@iem.at wrote:
From: IOhannes m zmoelnig zmoelnig@iem.at Subject: Re: [PD-dev] struct _canvasenvironment To: pd-dev@iem.at Date: Wednesday, July 13, 2011, 8:31 PM -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-07-13 20:11, Jonathan Wilkes wrote:
Hello, Â Â Â Why is "struct _canvasenvironment"
in g_canvas.c instead of g_canvas.h? I want to take a t_object inside g_text.c and-- if it's an abstraction-- get its name and dir. I can get the name but cannot get the dir because "struct _canvasenvironment" isn't in g_canvas.h. Would it break things if it were moved there?
maybe because it is considered an opaque type?
it's a way of telling you: "t_canvasenvironment is private property, do not trespass". you don't have right of ways and if the next time you drop by, the owner decided to change everything, you are not supposed to complain.
Oops, I overlooked canvas_getdir. But am I not supposed to "trespass" into this function since it's not in g_canvas.h?
mfgasdfr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4d5GoACgkQkX2Xpv6ydvR5CgCgmk4QxjBdeDW58g9G/KxVnVtT gfEAn0Rw8pouk0ikU4+DXVAEBBrY3+gn =Y2de -----END PGP SIGNATURE-----
-----Inline Attachment Follows-----
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev