Global Double Mouse Click Center与Global Mouse Click Center差异及报错原因咨询

Alright, let’s unpack this step by step— I’ve run into exactly this kind of issue with Blue Prism (given your mention of Application Modeller and Business Objects, that’s the tool we’re talking about) before, so I know where to look.

First, let’s break down what each action does, since that’s critical to understanding the error:

• Global Mouse Click Center: This is a single left-click operation. It works by locating the center of your target element, then sending one click command. It’s relatively lenient—even if the element is in a partially loaded state or has minor UI tweaks, as long as its core recognition properties match what’s in your Application Modeller, it’ll execute successfully.
• Global Double Mouse Click Center: This is a double-click action with stricter execution rules. After the first click, Blue Prism will re-verify that the element still matches your Application Modeller query before sending the second click. It requires the element to be fully interactive, with no temporary UI shifts, obstructions, or property changes between the two rapid clicks.

Since the single click works fine, here are the most likely causes for the double-click failure:

• Element properties shift after the first click: When you click your Edit(Java) element (like an input box), it might immediately update its state—for example, gaining focus which changes its border style, a dynamic attribute, or even its position slightly. Blue Prism’s double-click action checks the element’s properties again before the second click, and if those properties no longer match your Application Modeller setup, it throws the "no match" error. The single click doesn’t do this re-check, so it succeeds before the properties change.
• Timing/rendering delays: Double-clicks happen in an extremely short window. If your Java element takes a split second to re-render after the first click, Blue Prism will attempt the second click before the element is ready, leading to a failed match. Single clicks don’t have this tight timing constraint.
• Unstable recognition properties: The attributes you’ve set in Application Modeller for the Edit(Java) element might not be persistent. For example, if you’re relying on a temporary position value or a dynamic CSS class that changes on interaction, the double-click’s re-verification will fail. Single clicks might execute fast enough to catch the element before these properties shift.
• Strict interactivity requirements for double-clicks: Some Java controls have stricter rules for accepting double-clicks—they need to be fully active, with no background processes running on them. Single clicks might trigger even if the element is in a slightly less interactive state, but double-clicks won’t.

内容的提问来源于stack exchange，提问作者Andrés Gibson