AutoCAD 2010/2011/2012 DWG Format
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Hi all,
In AutoCAD (Mechanical or Electrical) 2012 I have my SNAP on. When there is no command active, also my cursor isn't "snapping". When I active a command, i.e. Line, then my cursor snaps.
When I end the command, also my cursor isn't snapping.
Anybody knows if this is a new setting in AutocAD 2012?
In the 2011 versions my cursor snaps when there is no command active.
Thanks!
John van Eeten
Solved! Go to Solution.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Yes, i want it to bounce! Creating electrical schematics with crosshair 100% and snap on. When no command acive, mainly to inspect if components are on the same heigth.
I have worked this way since release 12.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
It is changed for 2012, enough people complained about it to get it changed. I am surprised there is no "classicsnap" setting.
Simply start any draw command and inspect away.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I haven't found a way of reverting this, either. I guess one workaround is to just start a command (e.g. L [Enter]) and ignore it.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I find the new setting annoying as well since I use it as you do and use the snap (even when no command is active) to verify that certain things are of the same length or are on the same plane. If anyone finds a solution to this, please post up.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I. too, find this very annoying. At the minimum, there should be a "legacy" option or command to have the crosshairs snap to the grid when no command is active.
Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Its a good illustration of the troubles with software development. A group of people say "We DEMAND feature A!", so AutoDesk includes feature A. But this invariably inconveniences a good portion of those who like things the way they are so have no reason to speak out. So one small-ish group gets what they want, another small-ish group gets kicked in the... and the rest of us in the middle go "huh" and start wondering if we will end up in one group or the other the next time.
A switch setting for this would have been nice but I don't know if thats even possible.
If you are going to fly by the seat of your pants, expect friction burns.
Adopt. Adapt. Overcome. Or be overcome.

Re: No Snap when No Command Active??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Unfortunately, there isn't a legacy setting. Since AutoCAD now only honors the snap grip when prompting for a point (for easier selection while Snap is on), you need to enter a command like ID to identify the snap grid points.
We'll put in a request to add a variable to bring back the legacy behavior. We didn't get strong feedback on during the Beta period, but the point is taken to make sure we provide access to legacy behavior when we make a change like this.


