Comments on: Interesting ChangeWatcher Behaviour https://www.barneyb.com/barneyblog/2007/10/26/interesting-changewatcher-behaviour/ Thoughts, rants, and even some code from the mind of Barney Boisvert. Thu, 11 Sep 2014 09:58:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: barneyb https://www.barneyb.com/barneyblog/2007/10/26/interesting-changewatcher-behaviour/comment-page-1/#comment-48038 barneyb Wed, 14 Nov 2007 18:52:43 +0000 http://www.barneyb.com/barneyblog/2007/10/26/interesting-changewatcher-behaviour/#comment-48038 Manfred, You are correct, only the array reference itself is monitored, not the contents. The bit that surprised me was that the ChangeWatcher fired as part of setting the watched value, not as part of processing an event dispatched by setting the watched value (and therefore after the current call stack finishes). Manfred,

You are correct, only the array reference itself is monitored, not the contents. The bit that surprised me was that the ChangeWatcher fired as part of setting the watched value, not as part of processing an event dispatched by setting the watched value (and therefore after the current call stack finishes).

]]> By: manfred karrer https://www.barneyb.com/barneyblog/2007/10/26/interesting-changewatcher-behaviour/comment-page-1/#comment-47969 manfred karrer Wed, 14 Nov 2007 11:49:32 +0000 http://www.barneyb.com/barneyblog/2007/10/26/interesting-changewatcher-behaviour/#comment-47969 i think that is because flash do not inspect the contetn inside the array. and the actual array object has not changed, it is treated as an reference. otherwise it would cost a lot of performance to inspect the whole object (it could be a complex graph)... i think that is because flash do not inspect the contetn inside the array. and the actual array object has not changed, it is treated as an reference. otherwise it would cost a lot of performance to inspect the whole object (it could be a complex graph)…

]]>