Leaderboard

There will be screaming. Autodesk has just redefined the word "perpetual".

They are XML files but still readable if you open it a text editor. But they are more 'system' files, the export function in the customize palettes is an easier way to go for 'users' as atc files need to be loaded into the system by programming, whereas xtp files are more user friendly being imported/exported via a dialogue.

I prefer 15" screen with 1920x1080. I have had both 17" and 15" models and there is little difference in screen size, but a huge difference in weight and compactness. I'm always on a docking station so it's not too often I am in "laptop mode" where I'm actually doing production. I will stay 15" for good now that I made the switch on my last laptop. -TZ

Our color ctb has the 1st9 as black with various increasing thickness like old iso pens. The last few are greys as is, we have left the color as they are but just sort of know what works, all the colours are set to the same line weight 0.25. Yellow is the worst on white as mentioned, use 32 a nice Orange, some of the blues come out purplyish. Is that a word ? I have attached a sample we have around 5 different ctb's depending on the out put type fine for smll sheets a bit fatter for large sheets. Oh yeah the mono ctb you use the shift and drag over the pen settings to change colour lineweight etc dont do 1 at a time. DesignLaserCOLOUR.ctb

WOW the degree of accuracy in those instructions is underwhelming is it 130' or 136.8121????' WIth an approximate total length of 794.6157' or there abouts. I would worry about the 0.0001 difference between total length shown in the properties palette of 794.6157 as opposed to adding up the shown dimensions 794.6156 but this is just an approximation and I may have miss read the instructions.

Here's my interpretation using AutoCAD. Note that the total length of the green curve is about 900'. The 700' you reference does not include the 11° exit slope. The center of the 1000' bend is located on a line perpendicular to the 17° line.

Try the code below. Note 1: I haven't fully tested the code. I cannot run utmgeo.VLX as I use BricsCAD instead of AutoCAD. Also I would probably need a sample dwg with the highlighter block inserted in a 'feasible' location. If you have the source of the VLX and such a dwg please post them. Note 2: The highlighter block has to already be inserted before calling the SvUpdate command. (vl-load-com) (defun KGA_Sys_Apply (expr varLst / ret) (if (not (vl-catch-all-error-p (setq ret (vl-catch-all-apply expr varLst)))) ret ) ) (defun KGA_Sys_ApplyAlt (expr varLst) (not (vl-catch-all-error-p (vl-catch-all-apply expr varLst))) ) ; (SvUpdate_Browser "https://www.cadtutor.net/forum/forum/15-autolisp-visual-lisp-amp-dcl/") (defun SvUpdate_Browser (url) (if (or (and *SvUpdate_browser* (KGA_Sys_ApplyAlt 'vlax-get-property (list *SvUpdate_browser* 'visible)) ; Check if object is still available. (princ "\nUpdating StreetView in browser ") ) (and (princ "\nStarting StreetView in browser. Please wait... ") (or (setq *SvUpdate_browser* (KGA_Sys_Apply 'vlax-get-or-create-object '("internetexplorer.application"))) (prompt "\nError: Internet Explorer cannot be started ") ) (progn (setvar 'cmdecho 0) (command "_.delay" 2000) (setvar 'cmdecho 1) ) ) ) (progn (vlax-put-property *SvUpdate_browser* 'visible :vlax-true) (vlax-invoke-method *SvUpdate_browser* 'navigate url) ) ) ) (defun SvUpdate_CallBackModified (obj rea lst / pt) (if (and (vlax-read-enabled-p obj) (not (equal (vlr-data rea) (setq pt (vlax-get obj 'insertionpoint)) 1e-8)) ; Perhaps higher fuzz? ) (progn ; (print "SvUpdate_CallBackModified") (vlr-data-set rea pt) (SvUpdate_Move pt) ) ) ) (defun SvUpdate_Move (pt) (setq pt (utmgeo pt 6378160.0 298.25 18 "N")) (SvUpdate_Browser (strcat "https://www.google.com/maps?ie=UTF8&layer=c&cbll=" (rtos (cadr pt) 2 8) "," (rtos (car pt) 2 8) "&cbp=1,0,,0,5&z=16" ) ) ) (defun c:SvUpdate ( / obj pt ss) (if (and (or (setq ss (ssget "_X" '((2 . "highlighter")))) (prompt "\nError: 'highlighter' block not found ") ) (or (= 1 (sslength ss)) (prompt "\nError: more than 1 'highlighter' block found ") ) ) (progn (if *SvUpdate_objectReactor* (vlr-remove *SvUpdate_objectReactor*) ) (setq *SvUpdate_objectReactor* (vlr-object-reactor (list (setq obj (vlax-ename->vla-object (ssname ss 0)))) (setq pt (vlax-get obj 'insertionpoint)) ; Reactor data. '( (:vlr-modified . SvUpdate_CallBackModified) ) ) ) (SvUpdate_Move pt) ) ) (princ) )

A Display Name of $(if,$(and,1,$(getvar,ossnaphatch)),!.)OsnapHatch displays highlighted when on. Simple and easy alternative for displaying whether a system variable is On -vs- Off. For newer versions the proper macro would be ^P'setvar;osoptions;$M=$(if,$(and,1,$(getvar,osoptions)),$(-,$(getvar,osoptions),1),$(+,$(getvar,osoptions),1)) ^P with a Display Name of $(if,$(and,1,$(getvar,osoptions)),!.)OsnapHatch While OsnapHatch still works in 2019 it's hasn't been listed in help since before the 2015 versions.

Wouldn't you know it, post a negative answer then 2 minutes later you find the solution, try this in the command name section $(index,$(getvar, osnaphatch),"Current snap to hatch: off,Current snap to hatch: on") And place your other code in the macro section. PS nice idea, I'll be adding a few of these myself