getMarkerPos – Talk
Jump to navigation
Jump to search
mNo edit summary |
Lou Montana (talk | contribs) m (Text replacement - "Position2D" to "Position2D") |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
If the height above ground is always zero then maybe it should be stated that the position format is [[Position2D]] | If the height above ground is always zero then maybe it should be stated that the position format is [[Position#Introduction|Position2D]] | ||
[[User:Planck|Planck]] 20:55, 29 December 2006 (CET) | [[User:Planck|Planck]] 20:55, 29 December 2006 (CET) | ||
:Well, you do get it back as a three element array (even though z is always 0). So, while you can ''set'' the position as either 2D or 3D, the returned arrays is always 3D. | |||
:It also doesn't matter which z-value you use when creating a marker. Upon reading it it will still be 0 (e.g. if you do "XXX" setMarkerPos[11,22,33] you would still get [11,22,0] from getMarkerPos "XXX"). --[[User:Kronzky|Kronzky]] 21:11, 29 December 2006 (CET) | |||
Latest revision as of 16:55, 5 January 2022
If the height above ground is always zero then maybe it should be stated that the position format is Position2D Planck 20:55, 29 December 2006 (CET)
- Well, you do get it back as a three element array (even though z is always 0). So, while you can set the position as either 2D or 3D, the returned arrays is always 3D.
- It also doesn't matter which z-value you use when creating a marker. Upon reading it it will still be 0 (e.g. if you do "XXX" setMarkerPos[11,22,33] you would still get [11,22,0] from getMarkerPos "XXX"). --Kronzky 21:11, 29 December 2006 (CET)