Here's my point of view:<div><br></div><div>1) Theres a million and one ways.</div><div><br></div><div>2) If an array is changed by some pd-internal probably you can track that down in the "changer patch", thus you can control and know it.</div>
<div><br></div><div>3) Array comparison (as Jack noticed) is always possible, although slower.</div><div><br></div><div>4) You can hack into the object that you use for arraywriting (tabwrite?) and make a simple outlet that outputs some information about the last write (such as timestamp or other trick), then by simple comparison of the last know (stored by your patch) timestamp with the value from that outlet you can always know if the array was changed. But honeslty after writing this, it doesn't seem that elegant to me :)</div>
<div><br></div><div>Best of luck,</div><div>Pedri<br><br><div class="gmail_quote">On Mon, Dec 27, 2010 at 5:02 PM, Jack <span dir="ltr"><<a href="mailto:jack@rybn.org">jack@rybn.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Just output the value store in the array at the desire index (with<br>
[tabread]) before to write the new value (at the same index) and compare<br>
this new value with the old with [==]. If the result is false (0) then<br>
the array change. You get also the index that changed.<br>
Or i miss something ?<br>
++<br>
<br>
Jack<br>
<br>
<br>
<br>
Le lundi 27 décembre 2010 à 11:44 -0500, Ivica Ico Bukvic a écrit :<br>
<div><div></div><div class="h5">> Is there anything in the API that offers ability to detect when an array<br>
> has been changed and then act upon it? This would be quite useful when<br>
> using array as a multislider to change values. If there isn't I am<br>
> proposing providing an invisible send from array whenever it is changed<br>
> with the name <array_name>_changed. It could also send exactly which<br>
> element has changed.<br>
><br>
> Likewise, for the same reason, I would like to provide clipping of the<br>
> drawn items to the visible area but before I do so, is there a reason<br>
> one would want to keep outside elements visible as well despite their<br>
> distracting appearance?<br>
><br>
> Ico<br>
><br>
><br>
> _______________________________________________<br>
> <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
<br>
<br>
<br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Pedro Lopes (MSc)<br>contact: <a href="mailto:pedro.lopes@ist.utl.pt" target="_blank">pedro.lopes@ist.utl.pt</a><br>website: <a href="http://web.ist.utl.pt/Pedro.Lopes" target="_blank">http://web.ist.utl.pt/Pedro.Lopes</a> <br>
</div>