Over the last couple of days, I've noticed some odd behavior with my object snap settings when placing spot elevations. I typically have my object snap set for endpoint, center, and intersection by default and toggle on and off as needed or control-right click to snap to other points of objects. So what's happening currently is that if I have my object snap set to "on," I can place the first spot elevation and it will snap to an object. However, after placing that first spot elevation, I'm finding that my object snap is now set to "off," and all my preset snap settings are cleared out. So, not only do I have to turn object snap back on, but I also have to reselect my default snap-to points. Every time I place a spot elevation.
Am I doing something wrong here? Thanks.
Am I doing something wrong here? Thanks.
Accepted Answer
Roband,
During a technical support ticket last week, somebody else inadvertently found a cool feature with mleaders - if OSNAP is turned on before snapping to an object, the mleader will link itself to that object, like an associative dimension. So, we recently tweaked the spot elevation tool to take advantage of that and turn on OSNAP right before snapping the mleader to the spot block, and switch it back to the previously set OSNAP settings after. So now if you move the spot block, the mleader will move with it all the time.
Thanks for pointing out that issue with this tweak. We're going to track and fix that effect for this Friday's update.
-Amanda
During a technical support ticket last week, somebody else inadvertently found a cool feature with mleaders - if OSNAP is turned on before snapping to an object, the mleader will link itself to that object, like an associative dimension. So, we recently tweaked the spot elevation tool to take advantage of that and turn on OSNAP right before snapping the mleader to the spot block, and switch it back to the previously set OSNAP settings after. So now if you move the spot block, the mleader will move with it all the time.
Thanks for pointing out that issue with this tweak. We're going to track and fix that effect for this Friday's update.
-Amanda
Accepted Answer
Roband,
During a technical support ticket last week, somebody else inadvertently found a cool feature with mleaders - if OSNAP is turned on before snapping to an object, the mleader will link itself to that object, like an associative dimension. So, we recently tweaked the spot elevation tool to take advantage of that and turn on OSNAP right before snapping the mleader to the spot block, and switch it back to the previously set OSNAP settings after. So now if you move the spot block, the mleader will move with it all the time.
Thanks for pointing out that issue with this tweak. We're going to track and fix that effect for this Friday's update.
-Amanda
During a technical support ticket last week, somebody else inadvertently found a cool feature with mleaders - if OSNAP is turned on before snapping to an object, the mleader will link itself to that object, like an associative dimension. So, we recently tweaked the spot elevation tool to take advantage of that and turn on OSNAP right before snapping the mleader to the spot block, and switch it back to the previously set OSNAP settings after. So now if you move the spot block, the mleader will move with it all the time.
Thanks for pointing out that issue with this tweak. We're going to track and fix that effect for this Friday's update.
-Amanda
- Page :
- 1
There are no replies made for this post yet.
Contact
- Land F/X
Our software tailors AutoCAD® to the needs of landscape architects, irrigation designers, and other professionals. We automate your most tedious tasks and ensure accuracy, giving you more time to design.