leiafee wrote:
Are these little 'gotcha's something that come with experience or is their any info out there as to which actions are processed first?
When updating multiple variables at the same time, it is a good idea to try and isolate the variable actions to as few objects as possible, so that you have a much better indication of which updates are taking place in which order.
For example, in your problem publication, dropping a shape name onto the correct shape caused the name object to increase the <total> variable and the drop zone to increase the <correct> variable. However, unless you implement delays, you have no way of knowing which action is processed first (it happens to be the action on the text object, but I could only tell you this based on the behaviour of the problem publication).
However, if both actions are assigned to the same object, you can be sure that the top-most action will be processed first, followed by the next action in the list and this should eliminate any possibility of Variable Changed triggers interrogating variables before they have correctly updated.
Hooray...it's my 100th post!
I hope this helps. Please do not hesitate to contact me if you have any further queries.
Kind regards,