Your solution sounds like a better solution to me. Has it made it into the CVS?
/Nils [EMAIL PROTECTED] said: > I've made an (I hope) equivalent change. We try to handle this sort > of thing at a low level - thus the code that changes a component's > value calls DXChangedComponentValue, so that the data model > infrastructure can determine what is affected and has to be updated. > That code (in libdx/helper.c) was not handling invalid components > correctly. In particular, changing the value of "invalid positions" > may invaidate previously valid connections, and invalidating > connections may leave some positions unreferenced (and by convention, > invalid). In either case, the corresponding positions and connections > components are indirectly changed, and other stuff derived from them > (such as the data statistics component) require updating. By making > this change in helper.c, any other place that calls > DXChangedComponentValue will also be fixed.
