Hallo,
thanks for your effort.
Enrique Erne hat gesagt: // Enrique Erne wrote:
i had an idea about that. in the last version every sssad instance stores the content. this was not on purpose but it could be used to do a check on the event of saving. the loadband event is now exchanged and the check is when the user does the save. one disadvantage is that there is more sssad communication everytime a user saves. not sure if you want to go that way.
That's an interesting idea. I don't think, the added communication overhead would be that bad, but in my quick tests I found another problem (which may be possible to solve):
Say you have a [sssad A] watching a numberbox, then you change it, so that e.g. A = 100. If you then add another [sssad A] by duplicating the first, it is initialised to A = 0. This second A = 0 will overwrite the A = 100 if you press [set(
See attachement.
With the older [sssad], the 100 will be kept and on "set" will initialize the new A = 0 with A = 100. I think, that's the better behaviour. Hm, tricky ... ;)
Ciao
Frank Barknecht _ ______footils.org__