<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>hey List, Jonathan.<br></div>
<div> </div>
<blockquote><div>You start with a struct:[struct foo float x float y canvas a b]<br></div>
<div>Then create a scalar from this struct.<br></div>
<div>The scalar will have an "x" value, a "y" value, and a canvas "a" which gets filled with the contents of an abstraction "b.pd" that is somewhere in Pd's search path.<br></div>
<div>Now here's the neat thing-- inside the newly instantiated "b.pd" you can do this:<br></div>
<div>[loadbang]|[field x]|[print x]<br></div>
<div>When you instantiate that scalar above, its canvas "a" will print out the value of the "x" field for that scalar. In other words, the "a" canvas has access to all the field data of the scalar it belongs to.<br></div>
<div>The interface is exactly like [v], which means you can do this:<br></div>
<div>[loadbang]|[f]x[+ 1]|[field x]<br></div>
<div>This will _change_ the value of "x" for the parent scalar. So if you drew a little rectangle, when you instantiate your scalar you'll see it moving across the screen.<br></div>
</blockquote><div> </div>
<div>sounds really brainfunky! i'd love to see this in "action" in a screencast, cuz i just cant imagine how <br></div>
<blockquote><div><span class="highlight" style="background-color: rgb(231, 235, 242)"><span class="colour" style="color:rgb(42, 73, 125)">the "a" canvas has access to all the field data of the scalar it belongs to.</span></span><br></div>
</blockquote><div> </div>
<div>cheers<br></div>
<div>~/.jc <br></div>
</body>
</html>