Broadcast Click Action Options: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
m (1 revision(s))
mNo edit summary
Line 1: Line 1:
<font face="Arial">Scoped Broadcast (On by default)<br /> The Broadcast will transmit only to the Panel the Button is on and and Subsystems below it.<br /> Turn this off if you want a global transmission of the Broadcast.
'''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.


Continue Run After Broadcast<br /> After the Broadcast has been transmitted, the model will be continued automatically.


'''Continue Run After Broadcast'''
After the Broadcast has been transmitted, the model will be continued automatically.


Handle Without initialising Run<br /> In this case, if the Model is not running, the Broadcast will be transmitted, and if this option is set, then only the thread from any Broadcast Entries tuned into it will function, then the model run will terminate.<br />


'''Handle Without initialising Run'''


Can Send While Events Pending<br /> 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".
In this case, if the Model is not running, the Broadcast will be transmitted, and if this option is set, then only the thread from any Broadcast Entries tuned into it will function, then the model run will terminate.


'''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.
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.
----




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.<br /> </font>
<font size="2">idkbase note 10103</font>
----
 
[[Category:Broadcast/Scoped]]
[[Category:Broadcast]]
[[Category:Interaction (User)]]
[[Category:Interaction (User)]]
[[Category:Paint]]
[[Category:Paint]]
[[Category:Paint/Button]]
[[Category:Paint/Button]]
[[Category:Context Help]]
[[Category:Context Help]]
<font size="2">idkbase note 10103</font>

Revision as of 03:01, 12 January 2008

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.


Continue Run After Broadcast After the Broadcast has been transmitted, the model will be continued automatically.


Handle Without initialising Run

In this case, if the Model is not running, the Broadcast will be transmitted, and if this option is set, then only the thread from any Broadcast Entries tuned into it will function, then the model run will terminate.

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