the command is "Macro Run xxx", which calls another macro, in this case 'xxx' is the name. I always break
my programs down into modules, the first being a variables declaration module that then calls the macro
I want to run This way the variables are always available throughout your code (although you have to run or
call the variables module for each module you want to debug).
if you look below, there are code "snippets" that others have written and you can use them as modules...
http://www.macros.com/sharedmacros.htm
I took a "mouse move" module on the site and modified it and use it EVERYWHERE, because I find
macro express often "outruns" the ability of my computer, so i like to slow it down.
I also added the ability for the move to test for pixel colors, moving vertically or horizontally.
So look at the attached file
MouseMoveSEARCH
and at the top is documentation of how it works and what its doing, then
the "disabled" commands are the "calling routine" used to call MouseMoveSEARCH.
Note that there are variables shown in the "calling routine" BUT there are other variables
shown in the documentation section that are (or may be) needed.
You'll notice that MouseMoveSEARCH even calls other "modules", which I have attached too.
You will have to modify the "Case DL" (aka Divider Line) which is specific to the program I use,
BUT it simply looks for the type of cursor change that occurs when this "divider Line" is found.
I think I've covered everything needed as well as attached the files needed but note that I try
to document reasonably well so I may not respond to further inquiries
(not sure why I responded to this one!).
Good Luck - if you program reasonably well, it's simply a trial and error process of learning
the new code, in this case MacroExpress. I'm no wiz but it seems to have everything you
should need.
MouseMoveSEARCH.mex
MouseMove_ONLY.mex
CheckPixelColor.mex