Re: Release 0.2a0?

> What major obstacles remain before such a pre-release? Dallas: How are
> the models coming along?

Am I seeing right that the infinite recursion avoidance mechanism in event send
is not enough to avoid spurious push with models?

A) if prop1 of a component is bound to model mod modifying prop1 will

[Attrib.modify]

change value of mod
  this will trigger a change event
   one of the handlers is: push  prop1 for comp [1]
   ... other handlers ...
push prop1 [2, aggregate push at the end of Attrib.modify]

Is this correct ?

We could avoid to add the names of props bound to models in the name list
passed in [2], but when changing more than one single prop, the best thing
would be to avoid to call [1].

B) retrieving comp.prop1 can pull the value from the widget, then if prop1 is
bound to a modal its value is (should be) changed but this would trigger a
spurious push...

It seems we need a mechanism to identify handlers and a way to send an event
but ignoring some specified handlers.

Samuele.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf