On 09/09/2014 06:13 PM, Miller Puckette wrote:
I think it would be easy enough to implement (message boxes would simply save $0 and put it somewhere when the message was getting passed - with some ugliness about recursion to worry about.)
Can you give me an example of such a recursion so that I can try to think of a solution?
But I'd like to find a solution that somehow allows accessing $1, etc, from either context. I can't find a good design that would accomodate this. (And as always, when I can't think of a good design, I simply work on something else instead hoping I or someone else will think of something good in the future :)
M
On Tue, Sep 09, 2014 at 04:19:10PM -0400, Ivica Ico Bukvic wrote:
Miller et al,
The current code suggests that this should happen (binbuf_eval calls the appropriate function), but since canvas_setcurrent is never called, it fails and returns 0.
Yet, I wonder why message shouldn't be able to pre-parse $0 into a valid dollarzero (canvas instance), when there will never be a message one could send into it that could trump this argument (how would one specify an argument $0 anyhow)? I do understand that message is not meant to pre-parse values, but shouldn't this be an exception? That way one creating a message with an instance included does not have to go through the trouble of creating an [$0] object that needs to be packed with the rest of the list and then forwarded onward to a message object.
Thoughts?
If others are in favor of this idea, should this take place for all types of messages passed into message object (bang, list, anything, blob, etc.)?
-- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow DISIS, L2Ork Virginia Tech School of Performing Arts - 0141 Blacksburg, VA 24061 (540) 231-6139 ico@vt.edu www.performingarts.vt.edu disis.music.vt.edu l2ork.music.vt.edu
Pd-dev mailing list Pd-dev@lists.iem.at http://lists.puredata.info/listinfo/pd-dev