onMapSingleClick bugginess

[Mr.Peanut]

Is the onMapSingleClick command a bit buggy? I have the following script written for an example mission for a function I wrote.
The script is called in my init.sqs

Code: [Select]

#loop
onMapSingleClick {mapClick = +_pos}
@(Format ["%1",mapClick]) != "scalar bool array string 0xfcffffef"
onMapSingleClick {}
~0.5
_tmp = [[mapClick select 0,mapClick select 1],10,5] call SteepestDir
_steepestdir = _tmp select 0
_slope = _tmp select 1
"markPos" setMarkerPos mapClick
Me setPos mapClick
Me setDir _steepestdir
Hint Format["You are now at:\n Position = %1\n Facing Direction = %2\n Slope = %3",mapClick,_steepestdir,_slope]
mapClick = nil
_pos = nil
~1
goto "loop"
Now in both the mission editor and in pbo form the above script does not work all of the time.  Sometimes a single map click will be accepted, sometimes no map click will be accepted but most of the time it works as it is supposed to and accepts multiple clicks forever.

Without the small delays I put in it fails more often.  Is there something I am doing wrong or is this command a little buggy?

[General Barron]

Hmm... when you say that it sometimes "fails", what exactly do you mean? Does the hint get displayed, but nothing happens? Do you try clicking more than once, with slight pauses in between (to compensate for the pauses in your script)?

Anyways, I honestly have no idea what the problem would be, without actually running the script myself. I have never run into any bugs with this command, save the fact that it was poorly made. Although I think sometimes the actual mapclicks aren't always registered, especially if you are clicking during a high-lag environment, so that might count as a bug.

But I do think you are approaching the problem in a poor manner. Generally I think it is best to execute a separate script from the mapclick command, instead of using a global variable as a 'flag' to continue with the script.

So in init.sqs, you could put this:

onMapSingleClick {_pos exec "mapclick.sqs"}

And in 'mapclick.sqs', you put this:

onMapSingleClick {}
_tmp = [[_this select 0,_this select 1],10,5] call SteepestDir
_steepestdir = _tmp select 0
_slope = _tmp select 1
"markPos" setMarkerPos mapClick
Me setPos _this
Me setDir _steepestdir
Hint Format["You are now at:\n Position = %1\n Facing Direction = %2\n Slope = %3",_this,_steepestdir,_slope]
onMapSingleClick {_pos exec "mapclick.sqs"}


Now for my shameless plug: if you are going to be doing ANYTHING with the 'onmapsingleclick' command, then I HIGHLY recommend that you use my handler suite that I've made for it. It lets you easily do a number of things with the command that would otherwise be very tough, like working with multiple 'onmapsingleclick' events, limiting the number of clicks for a single event, etc. And I hope to add 'double-click' functionality soon too! Grab it here:

http://www.ofpec.com/editors/resource_view.php?id=850

[Mr.Peanut]

By fails, I mean nothing happens. A single click is not registered. A double click will still place a marker.

[Mr.Peanut]

This command is definitely bugged.

Try the following:
Put a marker on the map called "markPos" and a single unit.

init.sqs

Code: [Select]

onMapSingleClick {[_pos] exec "onMapClick.sqs"}
onMapClick.sqs

Code: [Select]

onMapSingleClick {}
_pos = _this select 0
"markPos" setMarkerPos _pos
onMapSingleClick {[_pos] exec "onMapClick.sqs"}
exit
Run the mission and start clicking on the map. Even with slow deliberate clicks, eventually it stops accepting single map clicks.

[Mr.Peanut]

Have posted above example on bugged commands thread.