Re: [ftm-devel] (ftm.o) persistency

[IOhannes m z. <zmo...@ie...>]

Norbert Schnell wrote:
> Ok, this is fixed now.
> 
> In ftm.o.c it looks a little bit like a hack but should stays (here  
> again) sufficiently elegant.
> Nevertheless, I had to change slightly the Max/MSP dependent code  
> (maxext.c:431).

i noticed that from the CVS logs and added the same to pddump.c

> 
> NOS
> 
> P.S.: Here is a little test patch (that could work in Pd):

hmm, it surprisingly it did _not_ work out of the box.
for one, i had to add a little header ("max v2" and "#N vpatcher..")
but still it did not work ("persistent" objects remained empty)...however:
banging the [ftm.m]s to initialize the [ftm.o]s, and then saving the 
patch (into a .pd file), keeps objects persistent.
on next load i can directly bang the last message and it prints two 
times the same ID (of fmat $three)


probably i'll investigate a bit on why the persistency does not work 
when loading max-patchers - but not before next week.

fmgasd.r
IOhannes

just fyi:

#N canvas 597 431 602 502 10;
#X obj 338 48 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X obj 338 72 ftm.m (($three size 3 3) fill 3.3);
#T _#ftm version 2 3;
#T _#scope begin;
#X obj 103 110 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144
-1 -1;
#X obj 103 134 ftm.m set 1 one 2 two 3 $three;
#X msg 51 40 print;
#X obj 51 72 ftm.o fmat @name three @persist yes;
#T _#obj 1 fmat;
#T _#mess 1 size 3 3;
#T _#mess 1 set 0 0 3.3 3.3 3.3 3.3 3.3 3.3 3.3 3.3 3.3;
#T _#set _#1;
#X msg 51 154 print;
#X obj 51 189 ftm.o dict @name d @persist yes;
#T _#obj 2 dict;
#T _#mess 2 set 3 _#1;
#T _#mess 2 set 2 two;
#T _#mess 2 set 1 one;
#T _#set _#2;
#X obj 111 238 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144
-1 -1;
#X obj 111 264 ftm.m (print (getid $three) (getid $d[3]));
#T _#scope end;
#X connect 0 0 1 0;
#X connect 2 0 3 0;
#X connect 3 0 7 0;
#X connect 4 0 5 0;
#X connect 6 0 7 0;
#X connect 8 0 9 0;