MiniRobotLanguage (MRL)
MDC. Command
Mouse Double Click (compatible engine with move)
Intention
MDC. simulates a Mouse-Move to, and a Double-Click at the target Position.
This Command simulates a Left-Double Click with the Mouse, using the Compatible Engine.
This command will simulate a real Mouse-Move, even with a "Human touch", if this is been set, using
OPT.HM|35
This is a are very realistic Mouse Move and a Mouse Double-Click at the target.
MDC. has therefore all the strong and all the weak sides of a typical Compatible Engine command.
Then the mouse pointer will move to the current "Active Point" and do the Click.
In most cases the "Active Point" is been set, by localizing a button or control or object.
In that case, the "Active Point" is in the center of the rectangular object.
You can find some more details on the "Active Point" and how to move it, here:
Some Hints:
If you need just one Compatible Engine click, use MLC.
If you prefer the mouse to "Jump" instead of slowly moving to the target, use MDI.
In case you can use the Direct Engine, MDE. is the command for you..
Syntax
MDC.[P1|][P2,P3]
Parameter Explanation
P1 - (optional) prototype coordinates
Prototype can be omitted or any of:
GROUP I (based on rectangular Area) Prototypes
"w" - choose RECT from last located Window (Child-/ or Top-Window)
"t" - choose RECT from last located Top-Window
"k" - choose RECT from last located Child-Window
"a" - choose RECT from last located Accessible Object (E8) (using SAO.,AGR.,NAV. etc.)
"g" - choose RECT from last located graphical Object (E9) (using QFR,, ANA., UNI. etc.)
"o" - choose RECT from last located Object/Window (any sort of)
"s" - use Screen-Coordinates, these will go over the whole Screen, including Dual- or Multi-Monitors
for these "Base-Prototypes" you can specify additionally fine-tuning using:
- Quadrant coordinates like:
MMV.o|{A2-B4}
- numeric numbers (positive and negative)
MMV.o|-20,90
and you can combine this:
MMV.o|-20,90 {A2-B4}
also there are three Prototypes that will do sort of "left-right" or "Mid" Positioning. These 3 can not be combined with each other.
"d" - Sort of LBO. - Positioning on the Left side of the current Rectangle.
"e" - Sort of RBO. - Positioning on the Right side of the current Rectangle.
"r" - Midpoint of the last RECT (default)
"u" - Move down by the size of the Windows-Titlebar
"v" - Move up by the size of the Windows-Titlebar
' Example (Combination):
MMV.oe|-20,90 {A2-B4}
GROUP II (based on Point) Prototypes
"m" - actual mouse-position. Usefull if the user moves the mouse somewhere and you want to act on that position.
"b" - last mouse-position, before last Move.
"p" - current "Active Point". (Default)
"l" - Last "Active Point".
Normally these commands just "Act" on the current "Active Point", but they do NOT Move the current "Active Point".
If you want to do so, just add the "x"-Prototype.
"x" - Set Active Point at this position.
If prototype is omitted, Screen-Coordinates are taken.
P2, P3 - (optional) x,y - coordinates
numeric coordinates, separated by comma. You can use
variable and Formula in (..). You can also use a
Point-Variable instead of two coordinates.
Example
'***********************************
' MDC.-Demo
'***********************************
STW.ct|PBWindowClass:0|TestApp
SCW.nct|2|Button|Button 2
MDC.p|(11*5),(-1*5)
ENR.
END.
Remarks
Mostly you do not need to specify the coordinates with MMV.or MLI. but you can directly write the coordinates into MLC., MLI., MRC. and MRI. Please see also BCS.
Limitations:
-
See also:
• 1.C Direct Engine and Compatible Engine
• MDE. - Mouse DoubleCLick Event
• MLE. - Mouse-Left-Click Event
• MLM - Mouse Left click Move (Invinsible)
• MLI - Mouse Left Click quIckly (Invinsible)
• MRC. / MRI. - Mouse-Right-Click