@midscene/computer 1.12.3-beta-20260902081623.0 → 1.12.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -76,6 +76,7 @@ export declare class ComputerDevice implements AbstractInterface {
76
76
  private xvfbCleanup?;
77
77
  private xvfbSignalCleanup?;
78
78
  private readonly inputDriver;
79
+ private readonly windowsPointerDriver;
79
80
  /**
80
81
  * On macOS, use AppleScript for keyboard operations by default
81
82
  * to avoid focus issues with system overlays (e.g. Spotlight).
@@ -86,6 +87,8 @@ export declare class ComputerDevice implements AbstractInterface {
86
87
  uri?: string;
87
88
  readonly inputPrimitives: ComputerInputPrimitives;
88
89
  constructor(options?: ComputerDeviceOpt);
90
+ private moveGlobalPointer;
91
+ private moveDisplayPointer;
89
92
  private focusKeyboardTarget;
90
93
  describe(): string;
91
94
  /**
@@ -111,15 +114,10 @@ export declare class ComputerDevice implements AbstractInterface {
111
114
  * DeviceName and captures in virtual-desktop coordinates, so secondary
112
115
  * displays — including those at negative offsets — are supported.
113
116
  *
114
- * Note: the process is left at its default (DPI-unaware) state on purpose.
115
- * Making it DPI-aware would require a runtime `Add-Type` C# compile (csc) —
116
- * the exact .NET-compiler dependency this PR removes by dropping
117
- * screenshot-desktop's polyglot .bat so it is intentionally avoided here.
118
- * As a result, captures on a scaled display come back at logical (scaled)
119
- * resolution. That is sufficient for the #2150 fix (the health check only
120
- * needs a successful capture). Per-monitor DPI / coordinate accuracy is a
121
- * separate Windows concern to be addressed in a follow-up with real-device
122
- * verification.
117
+ * The PowerShell thread is switched to Per-Monitor V2 before WinForms is
118
+ * loaded. Screen.Bounds, CopyFromScreen, and pointer movement therefore use
119
+ * physical pixels even when Windows display scaling is enabled. The native
120
+ * declaration is emitted in memory, so this does not require csc.exe.
123
121
  */
124
122
  private screenshotViaPowershell;
125
123
  size(): Promise<Size>;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@midscene/computer",
3
- "version": "1.12.3-beta-20260902081623.0",
3
+ "version": "1.12.3",
4
4
  "description": "Midscene.js Computer Desktop Automation",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -33,8 +33,8 @@
33
33
  "@computer-use/libnut": "^4.2.0",
34
34
  "clipboardy": "^4.0.0",
35
35
  "screenshot-desktop": "^1.15.3",
36
- "@midscene/shared": "1.12.3-beta-20260902081623.0",
37
- "@midscene/core": "1.12.3-beta-20260902081623.0"
36
+ "@midscene/core": "1.12.3",
37
+ "@midscene/shared": "1.12.3"
38
38
  },
39
39
  "optionalDependencies": {
40
40
  "node-mac-permissions": "2.5.0"