Re: New Excel BREAKS Prior Working Automation!

Author: Gene Wirchenko

Posted: 2017-03-17 at 13:41:12

At 18:53 2017-03-15, Kurt at VR-FX <vrfx@optonline.net> wrote:

>Hey there Gene!

>

>Guess great minds thing alike! Yup - been there - done that! Did the

>Wait command - but, alas - to no avail...

So do similarly deluded fools, but as that use case has

nothing, nothing to do with us, I will press on.

>Am working alternate kludge - but, today & tomorrow am in a 3D

>PRinting conference - so back to this problem on Fri...

You stated that the code worked on a computer that it did not

work on normally. Something about running the debugger did it. It

is possible that I/O had something to do with it. Maybe, it has to

be explicit. Some forms of the wait command will not wait, such as:

wait "Hello!" window nowait

What you are looking for is a condition that will break the

problem. *Then*, you refine it.

I may be telling you what you already know, but do so in case

you have overlooked something.

[snip]

Sincerely,

Gene Wirchenko

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/394089965b9bdf0d4d39aaf5acf4cb0a@mtlp000083

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2017 Gene Wirchenko