Maniphest T77284

Global commands to change markers shouldn't create a new marker
New, WishlistPublic
Actions

Tags

Subscribers

Killzone_Kid, AD2001

Assigned To

None

Authored By

swatSTEAM, May 22 2014

Description

Changing a marker with a global command (such as https://community.bistudio.com/wiki/setMarkerAlpha and https://community.bistudio.com/wiki/setMarkerPos, etc.), creates it for clients who don't have these markers.
Only https://community.bistudio.com/wiki/createMarker and https://community.bistudio.com/wiki/createMarkerLocal must create a new marker.

Details

Legacy ID: 2465051555
Severity: None
Resolution: Open
Reproducibility: Always
Category: Scripting

Event Timeline

Bohemia added a project: Arma 3.May 7 2016, 6:38 PM

swatSTEAM edited Steps To Reproduce. (Show Details)May 22 2014, 6:41 PM

swatSTEAM edited Additional Information. (Show Details)

swatSTEAM set Category to Scripting.

swatSTEAM set Reproducibility to Always.

swatSTEAM set Severity to None.

swatSTEAM set Resolution to Open.

swatSTEAM set Legacy ID to 2465051555.May 7 2016, 6:38 PM

Bohemia added a subscriber: AD2001.May 22 2014, 6:41 PM

Killzone_Kid added a subscriber: Killzone_Kid.May 7 2016, 6:38 PM

Been like this for ages. There are global commands and there are corresponding local commands for markers. Use only one type or mix at your own risk.