Clarify defer policy when schedule is called multiple times

Author: edwardalee

docs/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously

versioned_docs/version-0.5.0/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously

versioned_docs/version-0.6.0/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously

versioned_docs/version-0.7.0/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously

versioned_docs/version-0.8.0/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously

versioned_docs/version-0.9.0/writing-reactors/actions.mdx

@@ -171,6 +171,13 @@ For a `logical` action `a`, the tag assigned to the event resulting from a call
 
 For a **physical** action, the preliminary time is similar, except that _t_ is replaced by the current _physical_ time _T_ when `schedule()` is called.
 
+If no `<min_spacing>` has been declared, then the tag of the event is simply the preliminary time
+unless there is already an event scheduled for the same action with the same tag.
+In that case, a microstep is added to the tag.
+If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
+This process is repeated until there is no previously scheduled event with the same tag.
+This is equvalent to specifying a `<min_spacing>` of 0 with a `"defer"` policy.
+
 If a `<min_spacing>` has been declared, then it gives a minimum logical time
 interval between the tags of two subsequently scheduled events. If the
 preliminary time is closer than `<min_spacing>` to the time of the previously