Added the *scaleMouse* property so that host mouse coordinates can undergo an optional scaling transformation (default is 1.0)

versions/pcx86/1.36.0/pcx86-uncompiled.js

@@ -37277,7 +37277,7 @@ class ChipSet extends Component {
      *      scaleTimers:    true to divide timer cycle counts by the CPU's cycle multiplier (default is false)
      *      floppies:       array of floppy drive sizes in Kb (default is "[360, 360]" if no sw1 value provided)
      *      monitor:        none|tv|color|mono|ega|vga (if no sw1 value provided, default is "ega" for 5170, "mono" otherwise)
-     *      rtcDate:        optional RTC date/time (in GMT) to use on reset; use the ISO 8601 format; eg: "2014-10-01T08:00:00"
+     *      dateRTC:        optional RTC date/time (in GMT) to use on reset; use the ISO 8601 format; eg: "2014-10-01T08:00:00"
      *
      * As support for IBM-compatible machines grows, we should refrain from adding new model strings (eg, "att6300")
      * and corresponding model checks, and instead add more ChipSet configuration properties, such as:
@@ -37360,7 +37360,7 @@ class ChipSet extends Component {
         }
 
         this.fScaleTimers = parmsChipSet['scaleTimers'] || false;
-        this.sRTCDate = parmsChipSet['rtcDate'];
+        this.sDateRTC = parmsChipSet['dateRTC'];
 
         /*
          * Here, I'm finally getting around to trying the Web Audio API.  Fortunately, based on what little I know about
@@ -37646,7 +37646,7 @@ class ChipSet extends Component {
                 this.abCMOSData = new Array(ChipSet.CMOS.ADDR.TOTAL);
             }
 
-            this.initRTCTime(this.sRTCDate);
+            this.initRTCTime(this.sDateRTC);
 
             /*
              * initCMOSData() will initialize a variety of "legacy" CMOS bytes, but it will NOT overwrite any memory
@@ -55832,9 +55832,8 @@ class Mouse extends Component {
         super("Mouse", parmsMouse, Messages.MOUSE);
 
         this.idAdapter = parmsMouse['serial'];
-        if (this.idAdapter) {
-            this.sAdapterType = "SerialPort";
-        }
+        if (this.idAdapter) this.sAdapterType = "SerialPort";
+        this.scale = parmsMouse['scaleMouse'];
         this.setActive(false);
         this.fCaptured = this.fLocked = false;
 
@@ -55862,6 +55861,7 @@ class Mouse extends Component {
         this.bus = bus;
         this.cpu = cpu;
         this.dbg = dbg;
+        this.scale = cmp.getMachineParm('scaleMouse') || this.scale;
         /*
          * Attach the Video component to the CPU, so that the CPU can periodically update
          * the video display via updateVideo(), as cycles permit.
@@ -56257,17 +56257,27 @@ class Mouse extends Component {
     moveMouse(xDelta, yDelta, xDiag, yDiag)
     {
         if (this.isActive()) {
-            if (xDelta || yDelta) {
+            /*
+             * I would prefer to simply say "Math.round(xDelta * this.scale)", but JavaScript's round() function
+             * rounds negative numbers toward +infinity if the fraction is exactly 0.5.  All positive numbers are
+             * rounded correctly, so we convert the value to positive and restore its sign afterward.  Additionally,
+             * if the scaling factor turns a non-zero value into zero, we restore the value to its smallest legal
+             * non-zero value (thanks to Math.sign() again).  This ensures that tiniest movement of the physical
+             * mouse always results in at least the tiniest movement of the virtual mouse.
+             */
+            var xScaled = (Math.round(Math.abs(xDelta) * this.scale) * Math.sign(xDelta)) || Math.sign(xDelta);
+            var yScaled = (Math.round(Math.abs(yDelta) * this.scale) * Math.sign(yDelta)) || Math.sign(yDelta);
+            if (xScaled || yScaled) {
                 if (this.messageEnabled(Messages.MOUSE)) {
-                    this.printMessage("moveMouse(" + xDelta + "," + yDelta + ")");
+                    this.printMessage("moveMouse(" + xScaled + "," + yScaled + ")");
                 }
                 /*
                  * As sendPacket() indicates, any x and y coordinates we supply are for diagnostic purposes only.
                  * sendPacket() only cares about the xDelta and yDelta properties we provide above, which it then zeroes
                  * on completion.
                  */
-                this.xDelta = xDelta;
-                this.yDelta = yDelta;
+                this.xDelta = xScaled;
+                this.yDelta = yScaled;
                 this.sendPacket(null, xDiag, yDiag);
             }
         }