Page 1 of 1
Pixel Search bug
Posted: 09 Jan 2014, 17:10
by 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%
Re: Pixel Search bug
Posted: 10 Jan 2014, 11:31
by nnnik
Is anybody else receiving an Msgbox with the value 470, 713?
Re: Pixel Search bug
Posted: 10 Jan 2014, 11:53
by just me
Yes, I confirm (Win XP - AHK 1.1.13.00 U32).
Edit: But ErrorLevel is 1.
Re: Pixel Search bug
Posted: 10 Jan 2014, 12:44
by smorgasbord
470,
613713
,
On win 7, version 1.1.13.01
Re: Pixel Search bug
Posted: 10 Jan 2014, 14:09
by nnnik
Are you sure that it is 613?
Re: Pixel Search bug
Posted: 10 Jan 2014, 22:52
by smorgasbord
@nnnik
yes
amended.
Re: Pixel Search bug
Posted: 12 Jan 2014, 15:29
by nnnik
OK .This seems to be a bug.
Re: Pixel Search bug
Posted: 13 Jan 2014, 14:52
by Grendahl
470, 713
ErrorLevel 1
Win7 Ent x64 and Win7 Pro x64
AHK v1.1.11.00 (Unicode 64-bit)
Re: Pixel Search bug
Posted: 14 Jan 2014, 05:24
by lexikos
It'll be fixed in the next release.