@[Only registered and activated users can see links. Click Here To Register...]
In order to make it easier to port with lower resolution, perhaps add textboxes for users to input the X/Y coordinates manually or by using a Timer with HotKey.
[Only registered and activated users can see links. Click Here To Register...]
I made this auto worker feeder prior to the release of your script.
Just make a helpfile or a tutorial where to find the image in your screen and let the user find it themselves so the script will work on any resolution.
The sample HotKey for clicking the "..." to find the Worker Icon.
So yea, with this we can make a universal resolution script.
Of course you'll have to add each X/Y textboxes for each Pixel/images to find.
This will save time into converting the script and less support given to the users who is using your script because they can now tweak the script at will without touching the source directly.
In order to make it easier to port with lower resolution, perhaps add textboxes for users to input the X/Y coordinates manually or by using a Timer with HotKey.
[Only registered and activated users can see links. Click Here To Register...]
I made this auto worker feeder prior to the release of your script.
Just make a helpfile or a tutorial where to find the image in your screen and let the user find it themselves so the script will work on any resolution.
The sample HotKey for clicking the "..." to find the Worker Icon.
Code:
workHotkey = GetAsyncKeyState(Keys.Insert)
numWorkX.Value = MousePosition.X
numWorkY.Value = MousePosition.Y
Status.Text = "Locate worker icon && press {INS} Key to save."
If workHotkey = True Then
workHotkey = False
tmrWorkerHotkey.Stop()
Status.Text = "Worker Icon location has been saved."
End If
Of course you'll have to add each X/Y textboxes for each Pixel/images to find.
This will save time into converting the script and less support given to the users who is using your script because they can now tweak the script at will without touching the source directly.