I agree with others, I want multiple visibility states inside a dynamic block. One visibility state is not enough and has lead to me making weird operational features just to work around this subject and it confuses AutoCAD, our employees, and anyone who tries to modify these blocks every time. If I had multiple visibility states possible, this situation would be extremely easy. Unfortunately for now, I'll just keep trying to work around this problem .
There is the potential to do this out there from a free program.
Would need to check back to find it but try googling it. I never used it myself but it does exist thru a simple free lisp.
fix dim reassociate for angular dimensions . as it is , its really bad . angle direction is erratic ; often times it does not get the right angle at all . you end up erase and recreate angular dimensions .
add to your lisp routines. It's not on fly. Have to cancel to issue comamnd but it works well.
I have these lines in a MyStuff.lsp file that autoloads.
(defun C:ZF () (command "zoomfactor")) ;;ZOOMfactor
(defun C:ZF2 () (command "zoomfactor" "20")) ;;ZOOMfactor 10
(defun C:ZF4 () (command "zoomfactor" "40")) ;;ZOOMfactor 30
(defun C:ZF6 () (command "zoomfactor" "60")) ;;ZOOMfactor 60
(defun C:ZF8 () (command "zoomfactor" "85")) ;;ZOOMfactor 85
Your wish is Autocad's VTOPTIONS command. Also look a the VTENABLE system variable.
From autocad help files
The VTOPTIONS command Sets the options for smooth view transitions.
Enable Animation for Pan and Zoom
Makes a smooth view transition during panning and zooming. (VTENABLE system variable)
Enable Animation When View Rotates
Makes a smooth view transition when the view angle is changed. (VTENABLE system variable)
Enable Animation During Scripts
Makes smooth view transitions while a script is running. (VTENABLE system variable)
Sets the speed of a smooth view transition in milliseconds.
Set the minimum speed for a smooth view transition in frames per second. When a smooth view transition cannot maintain this speed, an instant transition is used to preserve performance.
We need to be able to use osnaps on survey figures. OSNAPS seem to randomly work on survey figures. For example: I can use the nearest osnap and my line will snap to a vertex on the survey figure several feet away. not necessarily even to the closest point or vertex. This is very frustrating to our users when we need to snap precisely to a figure.
Survey Figures in general are difficult to modify. Particularly adding points at specific locations and elevations. I can get the figure to use the point that I add but the linework codes for curves and offsets seem to be ignored.