LayOut 2027 Mac — Measurements keyboard input not working consistently

I’m experiencing an issue in LayOut 2027 for macOS with entering numerical values during drawing and editing operations.

Examples:

  • When moving/copying an object, entering a division multiplier such as /3 does not produce the expected array.

  • When drawing or resizing an object, typing a numerical dimension followed by Return sometimes fails to apply the value.

These operations worked as expected in previous versions of LayOut.

The problem appears to involve the Measurements input system.

Is this a known issue with LayOut 2027 on Mac? Are other users experiencing similar behavior?

Environment: macOS, LayOut 2027
Version/build: 27.0.267 64-bit
Expected behavior: Numerical input is accepted directly during drawing and editing operations.

Could you make a screen recording that includes the whole screen? Those actions are working ok on my Mac, using the same LayOut you are using. A screen recording might help me see what you are doing, that I may not be doing.

In this clip, I move the line with option to copy. Then type “/6” to divide the distance, and press Enter. But nothing happens. I also place the cursor into the Measurements box and try pressing Enter from here too, again no response.

In this second clip, I activate the line tool, click once to initiate the line, then move the mouse to set direction. Then I enter “3” for 3 inches, and press Enter. I try several times, pressing Enter once or twice each attempt. But value does not take and the line does not complete.

Check out this page for tips: Move tool tips

I think I see what the problem is. There was an issue where using the Enter key on the numeric keyboard wasn’t working. It does work now in internal builds we have. I’m not sure when the fix will be in a released version. For now you would need to use the Return key.

Indeed. I tried the Return key instead of Enter (on the numeric keypad), and it works as expected. Thanks for helping me figure that out! I’ll look forward to the fix in the next build. Cheers!