Keyboard increment setting bug
Illustrator 24.2.1
Mac OS 14.6 iMac Late 2015 27"
Same problem exists as of 24.2.1: the default for Keyboard Increment does not stick properly when units are set to Picas. My existing default of 0p1 (1 point) has changed to 0p0.9996 (0.9996 point), and any attempt to change it to 0p1 while in Picas does not stick. However, if units are Points, it stays correctly at 1pt, but change the units to Picas, the value changes to 0p0.9996.
UPDATE: this happens in other places than the Prefernce for Keyboard Increment, and also happens whether the units are Picas or Points. e.g. if Keyboard incremment is set to 1pt, using the arrow keys to move an object results in very imprecise positioning. hitting the arrow key once moves an object from 0 to 0.9996pt instead of 1pt. Hit it again and it moves to 2.0004pt instead of 2. However, hit it one more time and it goes properly to 3pt exactly, and so on. Problem exists in both unit setting, Picas/Points.
I have reverted back to 24.1.3 and all is fine.
Brad Fischer
shared this idea
-
Ton commented
Same problem with pixels as unit.
Create an RGB document based on an RGB preset and set in Preferences the keyboard increment to 1 px
Close the document and create a document based on a Print preset (uses mm in Europe), increment becomes 0,3528 mm
All New RGB documents with px as unit will have 1,0001 px as increment.
There is no warning.
It may not look like a lot, but it becomes visible when many objects are repeated using the arrow keys and Cmd (Ctrl) D
Keep the increments consistent in RGB and CMYK documents and don’t change them when another color mode is chosen. -
Richard
commented
I have this problem too. It seems that illustrator does not allow any point-pica combinations that don't end with a multiple of 3. I can make a box's width 1p3, 1p6 or 1p9, but if I try to make it 1p2 it comes out as "1p2.0004". The decimal places disappear when I switch the unit of measure to points and the erroneous decimal places reappear when I go back to picas.
I have disabled pixel snapping every way I can think of and it didn't make a difference.