My Macro Scheduler is not recognizing correct pixel colors

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
rusty9073
Newbie
Posts: 4
Joined: Sat Dec 26, 2015 4:38 am

My Macro Scheduler is not recognizing correct pixel colors

Post by rusty9073 » Sat Dec 26, 2015 4:53 am

Hi,

I have been a regular user of MacroScheduler for a long time. I have an older version (7.3) but it has always worked fine, until I upgraded to a new computer.

Now for some reason it is not recognizing the pixel color when I scroll over parts of the screen with the cursor. (Example, an area that is white and should read as 16777215 read as a different number).

This is happening in the recommend screen resolution of 1920 X 1200. If I switch to a much lower resolution (1280 X 720) this issue appears to be resolved.

It doesn't make sense to run a new computer in a subpar 1280 X 720 resolution. Does anyone know how I get MacroScheduler to recognize pixels in the proper 1920 X 1200 format?


Thanks for your help,
Nate

rusty9073
Newbie
Posts: 4
Joined: Sat Dec 26, 2015 4:38 am

Re: My Macro Scheduler is not recognizing correct pixel colo

Post by rusty9073 » Sat Dec 26, 2015 4:39 pm

Update: Upon further investigation, I have discovered that my MacroScheduler software appears to be recognizing correct pixel color ONLY in the 1280 X 720 resolution.

In all other screen resolutions it is giving sporadic pixel color identifications that not correct, rendering it useless to run macros dependent on screen pixel colors.

Anybody have an idea on how to resolve this?

User avatar
Dorian (MJT support)
Automation Wizard
Posts: 1417
Joined: Sun Nov 03, 2002 3:19 am

Re: My Macro Scheduler is not recognizing correct pixel colo

Post by Dorian (MJT support) » Mon Dec 28, 2015 11:30 pm

Hi Nate,

So just to clarify..

You're using Macro Scheduler v7
Which version of Windows are you using?

If it's a newer version of Windows, I would be very surprised if updating to Macro Scheduler v14 didn't fix this problem.

Maybe try downloading the v14 30 day trial and seeing if that fixes the problem?

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts