[messages] Edit: Re: [Module Design] Problems with Dynamic Property
ilyathebes at gmail.com
Thu Jun 9 21:09:40 CEST 2016
[This message has been edited.]
> Each trigger depends on the onmove keystroke and each time at least 2
> triggers are firing 1 for leaving a zone and 1 for entering another
> zone (so which came first? chicken or egg scenario).
Yes, Tim is right. And both of these triggers try to change the same
I change your module, and it works fine (in my humble opinion):
https://drive.google.com/file/d/0B5rEsE ... sp=sharing
That is what I've done:
1. Changed the logic of "Counted" property. Now it reflects the zone,
where a piece was taken into account. In other words it is merely clone
of OldZone property. By the way I renamed it to "CountedIn".
2. Separated the command, which changes "CountedIn" property (i.e.
"setC"), from trigger actions, that increases/decreases "TotalStepsPC#"
global properties. I made it by adding one extra Trigger Action (named
simply "onmove"), that fired all other Trigger Actions one by one and
only then changes "CountedIn" property.
3. Improved logic when piece being deleted.
Hope this what you need.
Read this topic online here:
More information about the messages