Disabling smart track points by double-tapping the cmd key doesn’t work if the cursor is over a smart track point - or between two smart track points (the grey lines appear). Double-tapping ctrl in the windows version (usually) works. @dan
Hmmm, your reply made me test some more… It actually seems to work in a parallel projection viewport, but not so good in a perspective viewport (when a tracking line is ‘active’) - fails always here. Do you see this?
Hi Philip - so far, still good here in Perspective views. Shout if you can think of anything else to try - and, does it not work correctly for you in a new, blank file, using say, the Polyline command? That is my simple test so far - if you have more specific conditions, let me know…
Ok, back home testing on my Mac… The perspective view thing was false alarm - it happens in all views. I can get the unwanted behaviour if I start, for instance, the line command (or distance - or whatever) and just activating smart track points by moving my mouse around and hitting osnap points (usually by mistake when modelling) - and doing it WITHOUT CLICKING. In that case I can’t disable the smart track points by double-tapping cmd. Double-tapping the cmd key seems to be working normally if i go ahead and SELECT the first point in the command.
Any luck now?
Hi @Philip
Disabling smart points by double-tapping the cmd key works perfectly on my iMac. Maybe some conflict and keyboard shortcuts or pointing systems?
Thanks Simon! I really don’t know what the problem might be. I have no ‘unusual’ shortcuts or anything - and the problem is 100 % repeatable on my Mac - with the conditions I mentioned above.
maybe your keyboard hooks up, dirddy for instance. try show keyboard overview in the language preferences of your system, which indicates each pressed button and tap the key several times, if it does not show each time you press its the keyboard.