Topic: The name game :: Object Snaps

[JohnK]

The object of this game is to list everything you know about the subject. Every post has to something different then what was previously listed or it can be labeled as "Duplicate entry!" in bold red letters (If no one notices that it was a duplicate entry, don't tell anyone). After the subject is exhausted, we will add up the duplicate entries and see who has the fewest.

Entries do not have to be limited to general knowledge or specific language problems, they can be anything you have discovered throughout your experiences or research.

[JohnK]

You can use the TAB key to cycle through available object snaps.

[CAB]

You can enter a snap over ride at the command line during a command.

Like this:

Code: [Select]

Command: line
Specify first point: mid
of
Specify next point or [Undo]: end

[Arizona]

Setting the system variable osmode to 0 will turn off osnaps.
F3 is the toggle

[Lin-Z]

you can use them inside the CAL command such as using osnaps to add a distance to a formula

[Chuck Gabriel]

Running osnaps can foul up the behavior of some lisp routines.  However, if you change the osnap settings in a program to avoid this, it's good manners to put them back the way you found them when you're done.

[MikePerry]

You can turn OFF OSnap functionality for Hatch Patterns with OSnapHatch ( AutoCAD 2005 or above ).

[ronjonp]

You can type in 'OS during a command to set transparently.

Shift+RgtClk shows osnap POP.

[grush]

Nearest should be removed from the POP menu.
Just my $4.07.

Pete

[Keith™]

If you miss your osnap override point, you must re-enter your override osnap before the program will snap to that point.

[whdjr]

If you type in or select the wrong snap option you can just click into empty space to null out that choice and allow for another snap option.

[David Hall]

osmode is very usefull to set osnaps quickly

[Shinyhead]

using transparent snaps on the command line with point filters can make simple macros work almost as well as full fledged lisp routines, only much smaller and simpler.

[Keith™]

osnaps can be accessed via LISP to return the appropriate osnap point even if osmode is set to 0.

[Bryco]

Non is the command line way of turning off snaps.

[Bryco]

F3 also turns off snaps

[Bryco]

Typing End  on the command line during a command will give you an end snap

[VerticalMojo]

Typing OS in the command line will pop up your osnap settings....

*cool game by the way. Learning at the same time.....

[Jeff_M]

To toggle OSNAPS on/off, as the F3 key does, in your program instead of saving/restoring the original value to/from 0:

Code: [Select]

(if (= 16384 (logand (getvar "osmode") 16384))
  (setvar "osmode" (- (getvar "osmode") 16384))
  (setvar "osmode" (+ (getvar "osmode") 16384))
  )


[Bryco]

Since nearest and perpendicular are dangerous snaps, I've set up F4 to be nearest, F5 to be perpendicular and kept on going. It doesn't take long to get used to  and surprisingly enough I use F6 "Cen" more than any other.
It's just safer to be in control of which snap I am using.

[Sdoman]

Back in the old days, when you accidentally typed "END" for a osnap when a command wasn't active, the next thing you'd see is a black DOS screen because AutoCAD ENDED!

[Birdy]

PJD: His shirt is covered with 'em!

[SDETERS]

Typing in Mbuttonpan and setting it to 0 will give you osnap commands when One clicks the middle mouse button!

[CADaver]

using running osnaps over large xrefs can tax less powerful systems to failure.

[Lin-Z]

in 2007 you have to have OSNAPs turned on to snap to attached DWF's

[Bryco]

Aperture controls the size of the object snap box, like saying how strong you want the magnet. To see this in action type aperture-> 50 then type APBOX and set it to 1. Cool? Yeah but it gets annoying.

[Keith™]

ObjectARX allows you to program custom osnaps according to your own needs (see my previous QuarterSnap project)

[Kerry]

The PURPOSE of Osnaps is to assist with the positional relationships between drawing elements

[Keith™]

Osnap (snapping to a point in relation to an object) is decidedly different from Snap (snapping to a point in relation to a drawing grid)

[Sdoman]

You can use direct distance and Osnaps to get an angle or direction.  Say for example you have a line drawn at some uncommon angle.  And you have some stuff you want to stretch along that angle.  Start the stretch command, select your stuff, hit enter, pick a basepoint somewhere on the angled line using NEAr or ENDPoint, then use NEAr and drag your cursor over the line in the direction you want, and type the distance.   As long as AutoCAD can find something to snap too, it will work, even if the snap too point is off screen.  This is especially useful when working in 3D.

[CADaver]

OSNAP searches the area enclosed by the APERTURE, and will select the feature nearest the intersection of the crosshairs that satisfies the osnap condition.

[Sdoman]

Many times when you want to Osnap to the INSertion point of a block that contains lots of attributes, AutoCAD will snap to the attribute insertion points instead of the blocks insertion point (they should have given text objects a unique osnap).  You can avoid this by preceding your INSertion osnap with a QUIck osnap. 

This can been done by typing at the command prompt QUI,INS using a comma to separate the osnaps.  Or it can also be done one snap at a time by using a toolbar or menu:  QUI<Enter>INS<Enter>.



[fixed typo]
[another typo <g> ]

[Bryco]

fro (from) can be used in conjunction w/ osnaps and while it does cool thangs it's too confusing to bother with (I hope it's only me that doesn't bother with it)

[Shinyhead]

Well....

I use fro and o'snaps in macros to give me control of how a routine works without needing lisp, its actually very handy. But for general command line usage no, its kind of a pain.

[Shinyhead]

Many times when you want to Osnap to the INSertion point of a block that contains lots of of attributes, AutoCAD will snap to the attribute insertion points instead of the blocks insertion point (they should have given text objects a unique osnap).  You can avoid this by preceding your INSertion osnap with a QUIck osnap. 

This can been down by typing at the command prompt QUI,INS using a comma to separate the osnaps.  Or it can also be done one snap at a time by using a toolbar or menu:  QUI<Enter>INS<Enter>.



[fixed typo]

That is something I am gonna have to play with, I have had issues with that of late.

[Chuck Gabriel]

fro (from) can be used in conjunction w/ osnaps and while it does cool thangs it's too confusing to bother with (I hope it's only me that doesn't bother with it)

This little gem predates the addition of the "from" functionality, but I still prefer it.  I'm sorry to say I have no idea who the original author is.  I'm sure someone here probably knows, since I've seen this routine in use in more than one office.

Code: [Select]

;;; This is a useful routine for obtaining a relative point.
;;; It can be used whenever an AutoCAD command requests a point.
;;; Just enter "(ref)" in response to the "...point:" prompt, and
;;; enter the desired base (reference) point and the relative/polar
;;; offset from that point.

(defun ref ()
  (getpoint (getpoint "\nSelect base point. ")
    "\nEnter offset or drag direction and select distance: "
  )
)


[SDETERS]

If you are a autocad user and do not use osnaps and have .001 or so gaps between all of your objects I am sure you would be drug out in the street and shot by the next person who works on your drawing!   :pissed:

[Sdoman]

The QUIck osnap isn't listed on AutoCAD's menus any more, so I am sure a lot of users don't know about it or have forgotten about it.  It is used as a modifier to the osnap that follows it.   Another situation where QUIck is useful, is when osnaping to entities embedded in large Xrefs.

[Bryco]

mtp or m2p is a new osnap-middle point between two points

[CADaver]

fro (from) can be used in conjunction w/ osnaps and while it does cool thangs it's too confusing to bother with (I hope it's only me that doesn't bother with it)

This little gem predates the addition of the "from" functionality, but I still prefer it.  I'm sorry to say I have no idea who the original author is.  I'm sure someone here probably knows, since I've seen this routine in use in more than one office.

Code: [Select]

;;; This is a useful routine for obtaining a relative point.
;;; It can be used whenever an AutoCAD command requests a point.
;;; Just enter "(ref)" in response to the "...point:" prompt, and
;;; enter the desired base (reference) point and the relative/polar
;;; offset from that point.

(defun ref ()
  (getpoint (getpoint "\nSelect base point. ")
    "\nEnter offset or drag direction and select distance: "
  )
)


I wrote this in 1987:

Code: [Select]

(defun ro ()  (getpoint (getpoint "\nReference point: ") "\nOffset from reference: "))
Along with this APPINT workaround

Code: [Select]

(defun ip (/ line1 line2 list1 list2)
    (setq line1 (entsel "\nSelect first line: ")
  line2 (entsel "\nSelect second line: ")
  list1 (entget (car line1))
  list2 (entget (car line2))
    )
    (inters (cdr (assoc 10 list1)) (cdr (assoc 11 list1)) (cdr (assoc 10 list2)) (cdr (assoc 11 list2)) nil)
)

[VerticalMojo]

Often a saying used when something comes at a shock or out of nowhere.

For example: O' snap! That guy just ran a red light!   

                                        or

                   O' snap! You just got dissed by that girl!

For more examples see the movie Zoolander.....