Control-O and Alt-FO key stroke problems

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

User avatar
Marcus Tettmar
Site Admin
Posts: 7395
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Tue Jun 11, 2013 6:49 am

Code: Select all

Why couldn't MS automatically detect the existence of graphics? I hope Marcus will help us resolve the puzzling myth.
?? The entire screen is graphics.

WaitReady monitors system messages. It can never be perfect, relies on assumptions, and as with all this stuff you need to use trial and error to determine what works best for your specific situation.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Tue Jun 11, 2013 7:03 am

Marcus Tettmar wrote:?? The entire screen is graphics.
Of course not. Most financial webpages containing a host of charts fit into this category, whereof the WaitReady>1 should be used.
My question:
If the screen contains plain text, why not shorten the WaitReady>1 time?

User avatar
Marcus Tettmar
Site Admin
Posts: 7395
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Tue Jun 11, 2013 7:41 am

Let me try again: As far as the computer is concerned, THE ENTIRE SCREEN IS GRAPHICS.

Text can be rendered in many different ways. WaitReady monitors a set of windows messages and waits for them to cease being sent for a time. The 1 simply tells it to monitor paint events. This has nothing specifically to do with graphics. Paint events will get sent when text is written to the screen and when a pixel turns red.

What you are asking about detecting graphics is non sensical since graphics exist at all times anyway.

You seem to misunderstand what WaitReady does and seem to have some fanciful ideal about graphics. Please read the WaitReady help topic which says NOTHING about graphics.

http://www.mjtnet.com/manual/?waitready.htm

The 1 simply tells it to include wm_paint events in its monitoring. These messages get sent whenever the screen changes. Doesn't matter what the screen looks like to you and me - text or blobs - it still gets "painted".

The reason the inclusion of paint messages in WaitReady is optional is that some apps never cease painting, and continually update their region. So to include paint events would hold things up indefinitely. Like I said, suck it and see. Trial and error. Find out what works for your specific situation. Whether the app shows text or pictures of trees, it makes no difference and is not enough to tell us whether it keeps painting or not.

Please read the manual.

We've now gone horribly off topic, so can we end there please.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Tue Jun 11, 2013 8:06 am

Marcus Tettmar wrote:We've now gone horribly off topic, so can we end there please.
In any case, thanks for your excruciately meticulous annotation as to WaitReady>1, the best I have ever learned from you. For you, you can tell apple from orage between graphics and "paint". For me, I got mixed up before your narrative above. Thanks again.

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