The current behavior of typed input in Rhino is to treat a space as Enter unless the space is in a quoted string. This becomes a problem for people who use the command line and have spaces in names, lengths (4’-1 1/2"). The need to quote the string is not easily discovered.
One solution would be to parse a single space as a space and a double space (tapping the space bar twice).
Pros: Command line users would be able to enter single spaces in the “obvious” way.
Existing users who have been tapping the space bar for Enter need to be retrained.
Some new users will wonder why they could not get two spaces by tapping the space bar twice.
I’m bring this up now because I have some length parsing bugs on my V6 bug list. The bug http://mcneel.myjetbrains.com/youtrack/issue/RH-23095 is a good example. One issue that has come up is that string that is displayed on a dimension when feet-inches display or unit names are appended cannot be typed when specifying lengths or coordinates.
What do people think about trying
- one space in command line input from the keyboard is treated as a space
- two spaces in command line input from the keyboard is treated as Enter
this for Rhino 6?