|
<< Click to Display Table of Contents >> Navigation: 3. Script Language > Mouse-Operations > !Input Engine > Direct Engine Mouse-Operations |
MiniRobotLanguage (MRL)
MIR. Command
Mouse Input Right Click (Input Engine)
Intention
The MIR. command is your go-to for simulating right mouse clicks without touching your actual mouse. It’s like having a secret assistant that can open context menus or trigger right-click actions for you, all while your mouse pointer stays where you need it.
What sets MIR. apart is its double-click trick: it sends the right-click command two ways at once. This makes it extra reliable for getting the job done, even if an application is picky about how it handles clicks. And since your real mouse doesn’t move, you can keep working or browsing without any interruption.
Use it to open menus in hidden windows, click disabled buttons, or trigger actions in spots your mouse can’t reach—like off-screen controls. It’s a handy tool for automating tasks that rely on right-clicks, such as copying text or accessing settings, without messing with your current workflow.
The click happens at the current "Active Point," usually set by finding a button or object first. Want to shift it? Check out MAP - Move Active Point.
Hints:
• Since it uses the direct engine, MIR. needs the target app to cooperate. Some JAVA apps might not respond.
• If MIR. doesn’t work as expected, try MRC. for a single-method click or BSC. for an alternative.
• Great for automating right-click tasks like opening context menus without moving your mouse.
Syntax
MIR.[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: MIR.o|{A2-B4}
- numeric numbers (positive and negative): MIR.o|-20,90
and you can combine this: MIR.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)
GROUP II (based on Point) Prototypes
"m" - actual mouse-position.
"b" - last mouse-position, before last Move.
"p" - current "Active Point". (Default)
"l" - Last "Active Point".
If prototype is omitted, Screen-Coordinates are taken.
"x" - Set Active Point to the Command-position.
P2, P3 - (optional) x,y - coordinates
numeric coordinates, separated by comma. You can use variables and formulas in (..). You can also use a Point-Variable instead of two coordinates.
Example
'***********************************
' MIR.-Demo
'***********************************
STW.ct|PBWindowClass:0|TestApp
SCW.nct|2|Button|Right Click Zone
MIR.
MIR.r|(15*2),(-8)
ENR.
Remarks
For automating right-click tasks, MIR. shines with its dual-click reliability.
Limitations:
Some apps might not respond to both click methods, but the dual approach boosts success rates.
See also:
• 1.C Direct Engine and Compatible Engine
• MLE. - Mouse-Left-Click Event
• MIM. - Mouse Input Middle Button
• MEM. - Mouse Event Middle Button Click