Esteban
2007-11-20 22:58:05
As far as i can tell, FindColorsSpiralTolerance isn't "defined" in Smart.scar, yet it seems FindColorsSpiralTolerence seems to work sometimes, sometime it doesn't. How is SMART finding those colors if Smart.scar isn't telling SCAR how to find the colors when the RS client isn't the active client?
Only thing i can think of is if FindColorsSprialTolerance uses GetColor, which is defined in Smart.scar.
Markus
2007-11-21 06:15:06
SetTargetDC(SmartGetDC); will let scar search in SMART's bitmap.
Call it before/in setupsrl;
mat_de_b
2007-11-21 12:34:20
What he means is that normally the Target for all functions is the RS screen, but by using the SetTargetDC function you tell scar to do the functions on the new RS screen so that things dont need to be redefined, this is what you would do if you wanted to search in a bitmap, for instance if checking for text… then you take a bitmap of the screen and then check that saving time
Infantry001
2007-11-21 14:57:02
And I supposed GetColor was originially hardcoded to only work on the client that the SCAR crosshair targets, so that's why they had to replace it in smart.scar?
Markus
2007-11-22 02:40:29
The replaced getcolor is only faster then scar's, but not necessary.
BenLand100
2007-11-22 22:42:37
From: Infintry001
And I supposed GetColor was originially hardcoded to only work on the client that the SCAR crosshair targets, so that's why they had to replace it in smart.scar?
Actually, thats an artifact of time. In Scar 3.06 that bug was fixed in Scar, however the overridden version stuck ;)