QENumericEdit does not work properly with Galil Motion Control PVs about qeframework HOT 1 OPEN

While you can set leading zeros and precision, the widget by default checks for the actual range of the PV and decides based on that what the minimum number of leading zeros and what the minimum precision is. So if your motor goes from -100000 to 100000 EGUs and your MRES is 0.0002, you'll end up with 6 leading zeros and 4 decimal places. If that was not the case you couldn't cover the whole range of movement.
The proper way to solve this is to set sensible limit values and MRES in motor record or have proxy PVs. However you can also un-check "autoscale" property of QENumericEdit widget which will ignore your PV values and only look at the values of leading zeros, precission, minimum and maximum properties defined for that widget.

I'll get back to you about the CTRL+C and CTRL+V.

from qeframework.