setMousePosition problem

[Gigan 1]

I found the one that seemed problem in setMousePosition command.

The mouse position set by using setMousePosition command might be different from the mouse position acquired in the dialog and mouse event handler.

When 3D Resolution and Interface size are changed from the default, the different situation is caused.

Verification:

createDialog and ctrlSetEventHandler (mouse handle)

setMousePosition [1.0,1.0]

The mouse position is acquired and displays it.

3D Resolution (100%)

This is normal.

3D Resolution (50%)

The acquired mouse position is different :(

[mandoble 1]

Confirmed, setMousePosition command is definitively broken.

[.kju 3245]

Please report in the A2 CIT.

[Gigan 1]

Thank you for the confirmation and the report.

Although it may not be a bug, as additional information, it seems to that script execution stops immediately after moving a mouse pointer using this command for a moment.

Since it probably does not have no less than 0.1 seconds, in the processing which does not require precision, it is not important, but prudence is required when precision is required.

[mandoble 1]

Already reported here in A2 CIT. Gigan, might be you want to update that with more related findings like the execution stop or if you prefer I can update my post there.

I understand this "freezing" effect affects only to the script executing it, so using a spawn command just to set mouse pos might be a workaround for that problem.

Might be a test demo mission will be required for CIT in order to demostrate that script freezing effect.