topic Re: Control precision of exported properties in Visual LISP, AutoLISP and General Customization Forum

Control precision of exported properties

Gorra — Tue, 25 Jul 2023 19:26:49 GMT

Hello,

With considerable assistance I have a functioning script that exports a specific block's properties and attributes. However, the x and y coordinates need to be to 5 decimal places. Currently the 'x' cuts off at the decimal, and the 'y' is coming out as scientific notation rounded to the nearest 10 (the value is in the 5-million range). I expect it's just a prefix I need to add to the relevant entities, but the code is here:

(defun c:splcblk ( / out)

(vl-load-com)

(defun _writefile (fn lst / f)

;actually writing the attributes to the csv

(cond ((and (eq 'str (type fn)) (setq f (open fn "w")))

;as long as (argument fn's type=str) and (SPLCBLK.csv is open for writing) then

(foreach x lst

(if (= 'list (type x))

(write-line

(apply 'strcat (mapcar '(lambda (z) (strcat (vl-princ-to-string z) ",")) x))

)

(vl-princ-to-string x)

)

(close f)

)

(defun sb (/ e name n ss)

(if (setq name "SPLICECLOSURE";;;selecting all dynamic blocks of this name

ss (ssget "_X" '((0 . "INSERT")))

n -1

out (ssadd)

)

(while (setq e (ssname ss (setq n (1+ n))))

(if (= :vlax-true (vla-get-IsDynamicBlock (vlax-ename->vla-object e)))

(if (= (strcase (vla-get-Effectivename (vlax-ename->vla-object e))) (strcase name))

(ssadd e out)

)

(if (/= 0 (sslength out))(sssetfirst nil out)(princ (strcat "No Dynamic Block found by the Name - " name)))

;(princ)

)

(defun core (/ s x a r)

(sb) ;selecting all splice closure blocks

(foreach x (vl-remove-if 'listp (mapcar 'cadr (ssnamex out)))

(setq a (vlax-invoke (vlax-ename->vla-object x) 'getattributes))

(setq r (cons (append (cdr (assoc 10 (entget x))) (mapcar 'vla-get-textstring a)) r))

)

(princ (_writefile ;calling the write to file function

(strcat (getvar 'dwgprefix) "SPLCBLK.csv")

(append '((x y z SPLICE_NUMBER ACTIVITY_NUMBER DROP_QTY DROP_FIBRE DROP_FIBRE_START DROP_FIBRE_END

SPARE_FIBRE SPARE_FIBRE_START SPARE_FIBRE_END

RES_1_ADDR RES_1_FIBRE RES_1_FIBRE_START RES_1_FIBRE_END RES_1_SPLC_ORDER

RES_2_ADDR RES_2_FIBRE RES_2_FIBRE_START RES_2_FIBRE_END RES_2_SPLC_ORDER

RES_3_ADDR RES_3_FIBRE RES_3_FIBRE_START RES_3_FIBRE_END RES_3_SPLC_ORDER

RES_4_ADDR RES_4_FIBRE RES_4_FIBRE_START RES_4_FIBRE_END RES_4_SPLC_ORDER

RES_5_ADDR RES_5_FIBRE RES_5_FIBRE_START RES_5_FIBRE_END RES_5_SPLC_ORDER

RES_6_ADDR RES_6_FIBRE RES_6_FIBRE_START RES_6_FIBRE_END RES_6_SPLC_ORDER

RES_7_ADDR RES_7_FIBRE RES_7_FIBRE_START RES_7_FIBRE_END RES_7_SPLC_ORDER

RES_8_ADDR RES_8_FIBRE RES_8_FIBRE_START RES_8_FIBRE_END RES_8_SPLC_ORDER

RES_9_ADDR RES_9_FIBRE RES_9_FIBRE_START RES_9_FIBRE_END RES_9_SPLC_ORDER

RES_10_ADDR RES_10_FIBRE RES_10_FIBRE_START RES_10_FIBRE_END RES_10_SPLC_ORDER

SPLICE_MODEL FDH_SPLICE SOURCE_SPLICEID POLEID SPLICE_TYPE NAPNUMBER LOCATION ADDRESS

)) (reverse r))

)

(core)

(princ)

)

Any help would be appreciated.

Thanks,

Gorra

Re: Control precision of exported properties

Kent1Cooper — Tue, 25 Jul 2023 19:46:03 GMT

Does increasing your LUPREC System Variable setting help? Or perhaps replacing:

(vl-princ-to-string z)

[which doesn't seem to have a precision argument, so I assume it's affected by LUPREC] with:

(rtos z 2 5)

[Maybe that last needs to be done only with a test of what it's looking at, and applied to numerical values but not text strings if Attributes are involved, but I haven't studied the code that closely.]

Re: Control precision of exported properties

Gorra — Tue, 25 Jul 2023 19:41:21 GMT

@Kent1Cooper I've tried setting it to 5, and moved it to various places in the code, but didn't change the output.

Re: Control precision of exported properties

Gorra — Tue, 25 Jul 2023 19:52:35 GMT

@Kent1Cooper Replacing it gives bad argument type error

Re: Control precision of exported properties

Kent1Cooper — Tue, 25 Jul 2023 19:53:59 GMT

It seems it must be related to the (vl-princ-to-string) function, but I don't know how to get it to use more decimal places, nor what controls how many it spits out if not the LUPREC setting.

Re: Control precision of exported properties

Kent1Cooper — Tue, 25 Jul 2023 19:55:07 GMT

@Gorra wrote:

@Kent1Cooper Replacing it gives bad argument type error

Yeah, I'm sure that would be when it hits an Attribute -- I was suggesting it for the X and Y coordinates, but there needs to be some differentiation.

Re: Control precision of exported properties

Sea-Haven — Thu, 27 Jul 2023 01:22:59 GMT

Where is (core) ? Maybe thats where decimals are being lost.

Re: Control precision of exported properties

Gorra — Thu, 27 Jul 2023 22:13:26 GMT

@Sea-Haven Hi, Core is defined in the second last paragraph(?) It's for calling the other functions.

Gorra

Re: Control precision of exported properties

CADaSchtroumpf — Fri, 28 Jul 2023 10:52:42 GMT

Without being able to test your lisp code, I suggest you change in your code at line 42

(setq r (cons (append (cdr (assoc 10 (entget x))) (mapcar 'vla-get-textstring a)) r))

(setq r (cons (append (mapcar '(lambda (x) (rtos x 2 5)) (cdr (assoc 10 (entget x)))) (mapcar 'vla-get-textstring a)) r))

Re: Control precision of exported properties

Gorra — Fri, 28 Jul 2023 15:36:38 GMT

@CADaSchtroumpf That worked, thank you.