Hi all,
I have a question to satisfy my own curiosity. I was doing a little reading through the recent (2014) help files and noticed OSMODE 1024. I am wondering what is the use for it? I have always used ( SETVAR 'OSMODE 0); is there actually a case where I would ever need 1024?
Thank you for any comments.
Solved! Go to Solution.
Solved by Kent1Cooper. Go to Solution.
@paullimapa wrote:do a search & you'll find:
http://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/osmode-bit-codes/td-p/881680
I believe that my question has been minunderstood.
I use (setvar 'osmode 0) to turn off Object Snaps, It works so well that I can't comprehend why the need for bit code 1024. The documentation says, "1024 = Clears all object snaps". It only seems redundant to me. Am I wrong?
Thanks again.
Then there are these links:
http://forums.autodesk.com/t5/autocad-2000-2000i-2002-archive/missing-osmode-variable/td-p/97413
Seem to have been at one time used (back as far as AutoCAD 2000 version) to identify object snaps combined with Quick.
Area Object Link | Dwg Setup | Feet-Inch Calculator
Exchange App Store
@mid-awe wrote:
....
I use (setvar 'osmode 0) to turn off Object Snaps, It works so well that I can't comprehend why the need for bit code 1024. The documentation says, "1024 = Clears all object snaps". It only seems redundant to me. ....
Back in my ol' 2004 version here, 1024 is listed in the OSMODE System Variable description as the bit code for the Quick mode, but searching Help for that turns up nothing to describe how you would actually use it, and it's not among the modes you can select in the Object Snap tab in the Drafting Settings box. If I recall from even older versions, I think that if you combine it with some other mode(s) [such as by typing in something like QUI,END,MID], it's supposed to grab the first Endpoint or Midpoint object-snappable location it "sees," without evaluating whether any other(s) may be closer to the selection point.
I don't think I've ever used it in over thirty years of using AutoCAD. It certainly doesn't seem like something that would mean anything as an OSMODE value all by itself. When I set OSMODE to 1024 [not with the Osnapmode selection box, since I can't, but with (setvar)], and go to draw something, there's no Osnap Aperture box, and if I assume it's there but off, and hit F3 to turn it on, up comes the Osnap mode-selection tab for me to select some mode(s), with none already selected. So by itself it does seem to have the effect of clearing other modes -- maybe that's why it's described that way in what you found. But that's exactly what happens if I set OSMODE to 0, too. So no, I don't see any use for it, either.
I believe the use is to allow snaps to be disabled temporarily without having to save and reset actual settings, similar to using NONE for the next pick.