Constant/Global Variables in acaddoc.lsp

[stusic]

I'd like to add a few lisp variables to my acaddoc.lsp file, but I'm not sure it'd work. For instance, if I set a variable to (getvar "dwgname") in acaddoc and make it a global variable, would it update the variable to reflect the new dwgname when I open another drawing? My goal is to make a field that has a diesel expression using this variable for our title blocks, but it won't work if it's holding the filename from the first drawing...

Thanks

[Tom Beauford]

If you're using a field why the need to set a variable? Do it all in the field and it will even update if you change the drawing name.

[stusic]

Well, I suppose dwgname was a bad example. Sorry about that.

What I want to do is isolate the name of the folder three folders up from where the drawing resides (the project number) and set that as a variable (i.e., "c:\projects\254789\units\piping\pipingdiagram01.dwg" would be "254789"), then use that variable in a field in the title block. But if it doesn't update when another project drawing is open, then it'd update the title block with the wrong project number.

Also, I realize it wouldn't be a diesel expression (my original idea on how to go about it), but a lisp variable.

[Opie]

Unless you propagate the variable using the vl-propagate function, the "global" variable is only for the drawing it was set. You would be able to have the same variable across multiple open drawings with different values per drawing.

[stusic]

Unless you propagate the variable using the vl-propagate function, the "global" variable is only for the drawing it was set. You would be able to have the same variable across multiple open drawings with different values per drawing.

I've heard that propagate may the way to go, but I don't know VL or how to use that function. Is it something easy to use for a non-vlisp hacker?

[Opie]

From my understanding of your request, I don't think that is what you would want to do. I am assuming you are making this global variable automatic based on the drawing. If you open up another drawing that is not part of the project and propagate the variable, you may get unexpected results.

[stusic]

From my understanding of your request, I don't think that is what you would want to do. I am assuming you are making this global variable automatic based on the drawing. If you open up another drawing that is not part of the project and propagate the variable, you may get unexpected results.

Yeah, I'm trying to avoid the unexpected results

I was originally thinking a diesel expression may work, which would update like it's supposed to, but I don't know that it can do the in-depth digging like lisp can that I need to get the folder name.

[rkmcswain]

Yeah, I'm trying to avoid the unexpected results

I was originally thinking a diesel expression may work, which would update like it's supposed to, but I don't know that it can do the in-depth digging like lisp can that I need to get the folder name.

I don't suppose your example of a path/filename is the real thing...?...meaning that the part leading up to the project # is a constant length?

If by chance it is, something like this should work.
$(substr, $(getvar,dwgprefix)$(getvar,dwgname), 14, 6)

[BlackBox]

For when file paths are not a constant length:

Welcome to AUGI!

Give this a try:

(vl-load-com)
(defun _FilePath->List (filePath / i folder folders)
  (setq filePath (vl-string-translate "\\" "/" filePath))
  (while (setq i (vl-string-search "/" filePath))
     (setq folders (cons (setq folder (substr filePath 1 i)) folders))
     (setq filePath (substr filePath (+ 2 i)))
     )
  (reverse folders)
  )

Example:

_$ (_FilePath->List "G:\\745 The name of the Project\\74534\\drawings\\")
("G:" "745 The name of the Project" "74534" "drawings")
_$

[stusic]

I don't suppose your example of a path/filename is the real thing...?...meaning that the part leading up to the project # is a constant length?

Ah, not that lucky this time. The folder changes often (but from the project name to the drawing it stays the same). Thanks tho'!