Broadcast Click Action Options: Difference between revisions
mNo edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
The Broadcast will transmit only to the Panel the Button is on and and Subsystems below it. Turn this off if you want a global transmission of the Broadcast. | The Broadcast will transmit only to the Panel the Button is on and and Subsystems below it. Turn this off if you want a global transmission of the Broadcast. | ||
'''Check Parents For Broadcast''' | |||
When the Broadcast is scoped it and cant find a Broadcast entry in the heirachy below the button panel, the engine will search up the heirachy for a Broadcast entry. | |||
'''Continue Run After Broadcast''' | '''Continue Run After Broadcast''' | ||
After the Broadcast has been transmitted, the model will be continued automatically. | After the Broadcast has been transmitted, the model will be continued automatically. | ||
'''Can Send While Events Pending''' | '''Can Send While Events Pending''' | ||
Line 30: | Line 32: | ||
[[Category:Interaction (User)]] | [[Category:Interaction (User)]] | ||
[[Category:Paint]] | [[Category:Paint]] | ||
[[Category:Context Help]] | [[Category:Context Help]] |
Latest revision as of 11:26, 30 August 2012
Scoped Broadcast (On by default)
The Broadcast will transmit only to the Panel the Button is on and and Subsystems below it. Turn this off if you want a global transmission of the Broadcast.
Check Parents For Broadcast
When the Broadcast is scoped it and cant find a Broadcast entry in the heirachy below the button panel, the engine will search up the heirachy for a Broadcast entry.
Continue Run After Broadcast
After the Broadcast has been transmitted, the model will be continued automatically.
Can Send While Events Pending
When paused, if any current time events are pending AND the system is in InterDyne mode, then attribute views and buttons will not respond to user interaction UNLESS their new option "Can Send When Events Pending".
This builds on the premise that a model does not normally pause until all zero time events have been processed, but can be forced to pause using a "Pausable 0 Delay" - in which case new broadcasts and attribute changes could impact badly on an incomplete process.
By default, the platform now blocks these broadcasts/changes, for safety, but these options above allow the new behaviour to be overridden at which point the modeller takes the risk for ensuring integrity.
idkbase note 10103