I just saw that Max's [table] object has an inlet and outlet on it. You can send the position to the [table] object and it'll output the value. Then it also has a second inlet for setting the value at that position.
I think this interface is really nice and simple. I looked around to find how to add these inlets and outlets to Pd's [table], but couldn't find where to do it. Is there any reason why this is a bad idea? Can anyone give me some pointers as to where I should add the inlets and outlet?
.hc
----------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
On Sat, Oct 29, 2011 at 03:43:48PM -0400, Hans-Christoph Steiner wrote:
I just saw that Max's [table] object has an inlet and outlet on it. You can send the position to the [table] object and it'll output the value. Then it also has a second inlet for setting the value at that position.
I think this interface is really nice and simple. I looked around to find how to add these inlets and outlets to Pd's [table], but couldn't find where to do it. Is there any reason why this is a bad idea? Can anyone give me some pointers as to where I should add the inlets and outlet?
Pd's [table] had an inlet loooooong ago. I don't know, why it was removed, but if needed, it's possible to wrap xlets into an abstraction.
Ciao
On Nov 1, 2011, at 10:30 AM, Frank Barknecht wrote:
On Sat, Oct 29, 2011 at 03:43:48PM -0400, Hans-Christoph Steiner wrote:
I just saw that Max's [table] object has an inlet and outlet on it. You can send the position to the [table] object and it'll output the value. Then it also has a second inlet for setting the value at that position.
I think this interface is really nice and simple. I looked around to find how to add these inlets and outlets to Pd's [table], but couldn't find where to do it. Is there any reason why this is a bad idea? Can anyone give me some pointers as to where I should add the inlets and outlet?
Pd's [table] had an inlet loooooong ago. I don't know, why it was removed, but if needed, it's possible to wrap xlets into an abstraction.
After some probing, I figured out what the table object is: its an instance of t_canvas/t_glist actually, with its own custom table_new() method. That's a pretty odd situation. I'm thinking I'll strip that out to make [table] an object in its own right, and then add inlets like [tabwrite] and an outlet like [tabread].
.hc
----------------------------------------------------------------------------
Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra
Le 2012-02-26 à 20:38:00, Hans-Christoph Steiner a écrit :
After some probing, I figured out what the table object is: its an instance of t_canvas/t_glist actually, with its own custom table_new() method. That's a pretty odd situation. I'm thinking I'll strip that out to make [table] an object in its own right, and then add inlets like [tabwrite] and an outlet like [tabread].
To be compatible with the current [table], this would need to support all of the methods of the canvases, just like tables already do.
______________________________________________________________________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
On Mar 27, 2012, at 11:56 AM, Mathieu Bouchard wrote:
Le 2012-02-26 à 20:38:00, Hans-Christoph Steiner a écrit :
After some probing, I figured out what the table object is: its an instance of t_canvas/t_glist actually, with its own custom table_new() method. That's a pretty odd situation. I'm thinking I'll strip that out to make [table] an object in its own right, and then add inlets like [tabwrite] and an outlet like [tabread].
To be compatible with the current [table], this would need to support all of the methods of the canvases, just like tables already do.
Supporting all is probably not needed, since [table] seems to act like a subpatch rather than a full canvas. For example, sending "menusave" to a [table] saves the whole patch that [table] is embedded in.
.hc
----------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
-
Frank Barknecht -
Hans-Christoph Steiner -
Mathieu Bouchard