@Bkndsdl wrote:
Ok, after further review, I see the code change, but forgive me, I'm confused........I don't understand if I need to load every instance of variables into the routine - essentially hard coding the routine - or if I can simply replace what I need with the command line when I want the routine to change something?
using the fully corrected version that I posted on: 05-17-2014 08:37...
You can do a number of things. bear in mind that the sub function that I provided : (change-ec317-continuation-AttsByVal) was a specific example to tie the options directly to your examples. You can create any such subfunctions to cover any number of conditions, including a sub in which you ask the user for input, then send the appropriate "switches" to the GJO_ChangeAttVals function.
Viable options for the GJO_ChangeAttVals function:
ValList is REQUIRED but we'll save that for last...
whereas BlkName, AttTag, and CtabFlag can each be a specified value or passed as nil
so, calling GJO_ChangeAttVals can take any of the following forms:
-> process only those blocks named "BlockName" and only those attributes with the tag name of "AttributeTag" in the current layout tab
(GJO_ChangeAttVals ChangeList "BlockName" "AttributeTag" T)
-> process only those blocks named "BlockName" and only those attributes with the tag name of "AttributeTag" in any layout tab
(GJO_ChangeAttVals ChangeList "BlockName" "AttributeTag" nil)
-> process only those blocks named "BlockName" and all attributes with a matching value regardless of the attribute tag name in any layout tab
(GJO_ChangeAttVals ChangeList "BlockName" nil nil)
-> process all blocks regardless of name and all attributes with a matching value regardless of the attribute tag name in any layout tab
(GJO_ChangeAttVals ChangeList nil nil nil)
-> process all blocks regardless of name but only those attributes with the tag name of "AttributeTag" in any layout tab
(GJO_ChangeAttVals ChangeList nil "AttributeTag" nil)
either or both of the BlkName or AttTag strings can contain multiple names:
(GJO_ChangeAttVals ChangeList "BlockName1,BlockName2" "AttributeTag1,AttributeTag2" nil)
or valid ssget wildcards (the attribute tag checker portion of the code works similar to ssget for wildcards)
(GJO_ChangeAttVals ChangeList "BlockName*" "AttributeTag*" nil)
Now to the ValList variable (which I was setting to "changelist" within the example function prior to passing to the GJO_ChangeAttVals function)...
-> passing this list would change all attribute values (regardless of the current value):
*** warning***
Passing the next list along with nil for the block name and nil for the attribute tag would set EVERY attribute in EVERY block REGARDLESS of it's current value to "Everything is Equal"... a very dangerous combination... so be sure that you are supplying either block name or attribute tag or both with this example
*** warning***
(list (cons "*" "Everything is Equal") )
in the remaining examples the "value to replace" (the first part of each cons list) is not case sensitive but the new string will be exactly what is in the second part of each cons list.
(list
;if the string is exactly "dog" replace it with "Animal"
(cons "dog" "Animal")
;if the string is exactly "fish" replace it with "Seafood"
(cons "fish" "Seafood")
;if the string is exactly "car" replace it with "Transportation"
(cons "car" "Transportation")
)
(list
;if the string starts with "dog" replace it with "Animal"
(cons "dog*" "Animal")
;if the string ends with "fish" replace it with "Seafood"
(cons "*fish" "Seafood")
;if the string contains "car" replace it with "Transportation"
(cons "*car*" "Transportation")
)
(list
;if the string contains exactly "dog" or "cat" or "pig" replace it with "Animal"
(cons "dog,cat,pig" "Animal")
;if the string contains exactly "fish" or "lobster" or "crab" replace it with "Seafood"
(cons "Fish,lobster,cRab" "Seafood")
;if the string contains exactly "car" or "truck" or "Train" replace it with "Transportation"
(cons "Car,TrUCK,train" "Transportation")
)
(list
;if the string begins with "dog" or "cat" or "pig" replace it with "Animal"
(cons "dog*,cat*,pig*" "Animal")
;if the string ends with "fish" or "lobster" or "crab" replace it with "Seafood"
(cons "*Fish,*lobster,*cRab" "Seafood")
;if the string contains "car" or "truck" or "Train" anywhere within it, replace it with "Transportation"
(cons "*Car*,*TrUCK*,*train*" "Transportation")
)
As you can see there are many, many different ways to use the single function...
Since you're scripting the routine you will need to pre-define the options and variables at some point, either within the routine as sub functions (as with the example that I provided), or by setting lisp variables with the script prior to calling the function, or by writing the writing the options during the function call...but how you choose to call the function and pass the ValList and other options is entirely up to you..
If you want to define the variables within the script instead of hard-coding and defining specific functions within the lisp file (and remember that I am not familiar with scripting so all I can do is outline the options) I imagine that it would go something like this:
open a drawing
load the lisp file
define a changeList in the document with something like: (setq ChangeList (list (cons "dog" "car") (cons "cat" "truck") (cons "fish" "train")))
call the function with something like: (GJO_ChangeAttVals ChangeList "BlockName" "AttributeTag" nil)
save the drawing
repeat...
Yet another option (and my recommended method): define a "temporary" lisp/script file for this run that defines your specific options and calls,
then your main script would look something like
open a drawing
load the main lisp file
load the temporary lisp/script file
if you enclosed the calls within a function in a temporary lisp file, call the function from the temporary lisp file
save the drawing
repeat...
If what you are trying to do gets too complicated then you can run the main function a couple of times, once with one set of options and/or ValList to do one specific replacement task (defined and called with one predefined sub function), then a second (or more) time(s) with a different set of options and/or valList to further modify the results (defined with additional predefined sub functions). With the use of a temporary lisp file for the specific needs of "this run" (as recommended) you can define many functions to run with each desired processing option and call each of them, or a single function that calls the main function many times, each time with different options, all without "cluttering up" your original reusable main lisp file.
Message me privately if you would like for additional explanations.
-Gary
BTW: I hope the formatting comes through... this stupid Discussion Group decided that my creds weren't valid anymore when I went to submit it and I had to rebuild the post by copying to the contents to notepad then putting it all back together.
Gary J. Orr
(Your Friendly Neighborhood) CADD/BIM/VDC Applications Manager
http://www.linkedin.com/in/garyorr
aka (current and past user names):
Gary_J_Orr (GOMO Stuff 2008-Present); OrrG (Forum Studio 2005-2008); Gary J. Orr (LHB Inc 2002-2005); Orr, Gary J. (Gossen Livingston 1997-2002)
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
