The reason for 2 not working is that the editing commands were not
meant to be used programmatically, and have only been retrofited to be
used like that. Since the assumption was that the editing commands
would be triggered by a human, the code assumes that the patch is
visible when editing.

For #3, I'll see if I can debug that, I'm trying to fix as many GOP
bugs as possible with the Pd-extended 0.42.5 release.

.hc

On Jan 22, 2010, at 8:05 AM, Marco Donnarumma wrote:

Hi list, I'm working on dynamic patching with nested GOP subpatches
(developing a meta-friendly interface). I noticed this weird behaviour of GOP subpatch (I'm not sure but it
can be the same bug Hans was talking about on the list few days ago). Take a look at the attached ex. The first message works fine. The second message works only if the GOP subpatch is open. I guess
this is fine and it has to deal with "vis 1/0". But the weird thing happens with the third message. The message
actually works but the GOP is not updated (and it will never be
unless you save, close and reload).

I think I re.invented the wheel with this report, but I would like
to understand "why" this happen.

(this time setup: winXp, Pd-ex.41)

thx

-- Marco Donnarumma aka TheSAD

Independent New Media Arts Professional, Performer, Teacher -
Edinburgh, UK

LAB: http://www.thesaddj.com | http://cntrl.sourceforge.net | http://www.flxer.net

EVENT: http://www.liveperformersmeeting.net <3.2.cut_paste-gop.pd>_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

If you are not part of the solution, you are part of the problem.