Hi, I'm revising the helpfiles, and I noticed some weird behavior while looking at pointer-help.pd:
Hook up a [get template1 y] to the first pointer example.
Traverse and click "next" to the end of the list.
Get happily outputs the y field for template2 without error.
Which makes me wonder- why must template names be given as arguments to get/set/setsize/getsize? Template names in [pointer] already give you traffic control.
It would be a lot handier if you could just specify a field, and leave it up to the user to provide pointers to ds instances that have that field. Bonus: you could have a bunch of different ds's in a window, and poll all x and y coordinates with a single [get].
-Jonathan
The idea was originally so that the 'get', etc, objects could look up the field offset and type in advance to be more efficient. I've never implemented that though.
AND I do want to make an out so that you don't have to specify it, anyway.
cheers Miller On Sun, Jul 12, 2009 at 01:17:58PM -0700, Jonathan Wilkes wrote:
Hi, I'm revising the helpfiles, and I noticed some weird behavior while looking at pointer-help.pd:
Hook up a [get template1 y] to the first pointer example.
Traverse and click "next" to the end of the list.
Get happily outputs the y field for template2 without error.
Which makes me wonder- why must template names be given as arguments to get/set/setsize/getsize? Template names in [pointer] already give you traffic control.
It would be a lot handier if you could just specify a field, and leave it up to the user to provide pointers to ds instances that have that field. Bonus: you could have a bunch of different ds's in a window, and poll all x and y coordinates with a single [get].
-Jonathan
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Jonathan Wilkes -
Miller Puckette