Bug? Dirty state changes when abstraction is modified

Jun 29, 2007 at 9:52am

Bug? Dirty state changes when abstraction is modified

Hi all,

It seems that when I modify the contents of an abstraction, the dirty state of the containing patch is set to 1. I’d say this is unwanted behaviour because saving the patch won’t save the abstraction.

Here is an example:

– save as ‘test’

#P message 109 75 69 196617 brgb 0 255 0;
#P message 23 75 69 196617 brgb 255 0 0;
#P newex 23 51 41 196617 sel 1 0;
#N comlet (bool);
#P inlet 23 32 15 0;
#P user jit.fpsgui 23 99 101 196617 0;
#X setrgb 31 31 31 0 255 0 234 234 234 4 4 4;
#P connect 2 1 4 0;
#P connect 3 0 0 0;
#P connect 4 0 0 0;
#P connect 2 0 3 0;
#P connect 1 0 2 0;

– save as ‘getdirtystate.js’

function bang()
{
outlet(0, this.patcher.wind.dirty);
}

- main patch:

#P newex 31 154 58 196617 print dirty;
#P comment 149 115 100 196617 4) report dirty state;
#P comment 47 115 100 196617 2) report dirty state;
#P button 31 115 15 0;
#P newex 31 134 94 196617 js getdirtystate.js;
#P toggle 25 36 15 0;
#P newex 25 57 26 196617 test;
#P comment 42 36 201 196617 3) change color of fpsgiu inside abstraction;
#P comment 54 57 100 196617 1) open abstraction;
#P connect 3 0 2 0;
#P connect 5 0 4 0;
#P connect 4 0 8 0;

Can you confirm?

Thanks,
Mattijs

#32679

You must be logged in to reply to this topic.