Typing units in Dimension Box triggers tools instead
-
In the UK/USA/IR/etc [the civilized world
] it'd be:
10m,20m
Whereas in many other EU states, several Asian places etc it's
10m;20mWhat are your locale settings ?
You use a ; when your decimal point is set as a , otherwise you use a , when your decimal point is set as a .When you previously installed SketchUp did you select the icon for the installer's exe file, then right-click > context-menu > "Run as administrator..."
If not, then close SketchUp, do the above installation steps, when prompted choose 'Repair'...
Is that any better ?
-
I think that you mean ; as a value-separator rather than the decimal-separator, which is either a . or a , - when the value-separator is either a , or a ; respectively...
As you say you have recently updated some MAC 'Xcode' things, then has that somehow changed some system settings ?
In SketchUp if you draw a line and enter a length of 1.234 [or perhaps 1,234] and then use Entity Info to get its current length, is it indeed 1.234 units long ?
On a PC - and presumably a MAC - there are system settings to determine which characters are used for decimal-points and values delimiters ???
What are yours ? -
TIG, thanks for your answer. I realize my post was incomplete.
I am using sketchup pro 2017 17.2.2554 on macOS Sierra 10.12.3 (so, no "run as admin")
I am well aware of the different decimal points between the civilized world (using the metric system) and that other part of the world (using an archaic unit system)
Being part of the former, I use and have always used the ; as my decimal separator.Sorry to say but the problem isn't at all here. I do not even reach that point. As soon as I type an 'm' for meter or 'c' for the first letter of centimeter, it triggers the move tool or the circle tool.
I could reproduce the same behavior with the line tool and the tape measure tool requiring only one numerical input (so no separator).
This is clearly a problem of SU not recognizing the context of dimension input (or so it appears).SU behaved normally yesterday. The problem appeared just today. The only modification I applied to my machine in between was updating Xcode (and did not even open it since then).
Hope it makes it any clearer.
-
TIG: Oups. I edited my post while you were answering.
I am sorry to say, but I think you should read my answer more carefully. this has nothing to do with decimal point. I don't even reach the decimal point. As soon as I type m or any other "shortcut" letter, it triggers a tool. As another example procedure I have just executed now:
I want to draw a line 10 meters long
'L' triggers the line tool
click to start
drag
typing 10
as soon as I type 'm', it triggers the line tool.Reproducible with tape measure tool (requiring as line only one numerical input (no input separator involved) and I am sure others too.
I am typing only positive integers as inputs.This is not the normal behavior of sketchup.
I have spent an hour and a half on internet searching for an answer, carefully re-reading docs, before posting here. -
I'm now starting to think this issue is related to some MAC settings...
Where key-presses did unexpected things...I recall something being reported like this before...
I have PM'd some MAC-aficionados to see if they have any better ideas...
-
I should probably not have chosen an example involving multiple data at first, as this caused confusion obviously.
I have no problems with decimal values. A 2.5mm line (sorry, 2,5 in my part of the world) is indeed as long as it is supposed to be...
No locale change. I haven't even opened Xcode since. I mentionned it to be exhaustive. Anyway, this is not the problem in question. -
I now have one of our MAC gurus looking into it...
so wait for the next exciting installment [as they say !] -
First time this happens to me ever (in many years). As to SU 2017, I have been using it almost from the beginning, and this happens just now... Anyway, thanks for your concern
-
I confirm this is probably due to macOS update, since it works as it should on my windows machine and it used to work normally on my mac until now.
-
I use a Mac (macOS Sierra 10.12.3, SU 2017 Pro M2, Xcode 8.2.1) and I can't reproduce this issue. That doesn't mean it wasn't triggered by the update, but it depends on something specific to your system. I have no clue what, though.
Advertisement