Bug: Value behaviour acts as a pointer in broadcast message
-
When you broadcast a value behaviour, it broadcasts the value it refers to rather than the value it got at the time of running. An example:
The message and default text should be the same, since they are both the value of the Value behaviour; but while message is correctly showing the text that the box container stored at the time the value behaviour ran (Set Input Field4), default text is erroneously showing the text the box container only stored after the Value behaviour ran (Set Input Field5).
This indicates that the message being broadcast is what the value behaviour references, rather than its current value.
-
When you broadcast a value behaviour, it broadcasts the value it refers to rather than the value it got at the time of running. An example:
The message and default text should be the same, since they are both the value of the Value behaviour; but while message is correctly showing the text that the box container stored at the time the value behaviour ran (Set Input Field4), default text is erroneously showing the text the box container only stored after the Value behaviour ran (Set Input Field5).
This indicates that the message being broadcast is what the value behaviour references, rather than its current value.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login