deleteMarkerLocal: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class='command_description'>" to "<dl class="command_description">") |
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
||
| Line 30: | Line 30: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dt></dt> | |||
<dd class="notedate">Posted on 7 January, 2012</dd> | <dd class="notedate">Posted on 7 January, 2012</dd> | ||
<dt class="note">[[User:HomerJohnston|HomerJohnston]]</dt> | <dt class="note">[[User:HomerJohnston|HomerJohnston]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
Unproven: I believe that if you use this command on a globally-created marker, and subsequently another machine executes a global command on the same marker (e.g. setMarkerPos), then the marker will be re-created on the machine it was previously deleted on. Can result in confusing marker behaviour. | Unproven: I believe that if you use this command on a globally-created marker, and subsequently another machine executes a global command on the same marker (e.g. setMarkerPos), then the marker will be re-created on the machine it was previously deleted on. Can result in confusing marker behaviour. | ||
Revision as of 21:41, 5 June 2021
Description
- Description:
- Description needed
- Groups:
- Markers
Syntax
- Syntax:
- Syntax needed
- Parameters:
- markerName: String
- Return Value:
- Return value needed
Examples
- Example 1:
deleteMarkerLocal "Marker1"
Additional Information
- See also:
- createMarkerLocaldeleteMarker
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on 7 January, 2012
- HomerJohnston
- Unproven: I believe that if you use this command on a globally-created marker, and subsequently another machine executes a global command on the same marker (e.g. setMarkerPos), then the marker will be re-created on the machine it was previously deleted on. Can result in confusing marker behaviour.