Pixel Search bug

[nnnik]

Correct me if Im wrong, but the OutputVarX/Y variables of the PixelSearch command should be empty if no match was found right?
But that doesnt seem to be the case as long as you use fast mode:

Code: Select all

PixelSearch, x, y, 470, 400, 480, 712, 0x555555, 0, Fast
MsgBox, %x%, %y%
PixelSearch, x, y, 470, 400, 480, 712, 0x555555, 0
MsgBox, %x%, %y%

[nnnik]

Is anybody else receiving an Msgbox with the value 470, 713?

[just me]

Yes, I confirm (Win XP - AHK 1.1.13.00 U32).

Edit: But ErrorLevel is 1.

[smorgasbord]

470, 613713
,
On win 7, version 1.1.13.01

[nnnik]

Are you sure that it is 613?

[smorgasbord]

@nnnik
yes
amended.

[nnnik]

OK .This seems to be a bug.

[Grendahl]

470, 713
ErrorLevel 1
Win7 Ent x64 and Win7 Pro x64
AHK v1.1.11.00 (Unicode 64-bit)

[lexikos]

It'll be fixed in the next release.