On Thursday, October 28, 2004, at 09:15 AM, MAU wrote: > If you use keyboard stroke macros the problems may come from > different processor speeds. Last August I upgraded to a much faster > PC and found that some of my macros would not always (or never) > work. I traced this to the fact that they were executing too fast > (i.e. before some menus, windows or dialogs would actually pop up) > and had to adjust PowerPro's "typing speed". In same cases I even > had to include a /wait/ command so that macro execution would > actually wait for the target application/window to get focus back or > to open and get focus (i.e. wait active "Sorting Office*").
It would seem that this is the case for me, though the machine with the problem is the slower of the two. One has a 3GHz P4 processor, while the other has a 2.2Ghz Celeron. The slower machine seems to be executing too quickly, so I put in a wait command and that hasn't helped. <shrug> I've just about given up getting that macro to work. It involves bringing windows in and out of focus as well as copying and pasting window contents. -- -=[ Allie ]=- ... Happiness isn't getting what you want, it's wanting what you got ________________________________________________________ Current beta is 3.0.2.2 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
