Help please. LISP error.
@Anonymous wrote:
.... The error is:
; error: bad argument type: stringp nil
How do I figure out what the problem is? This is not much information to work with.
....
It's some information to work with.... It means that some function that wants a text string to work with is being given nil instead. Probably some variable that is supposed to hold a text string [it could be a Layer name, a Block name, the content that's supposed to go into of a piece of Text or an Attribute, or a variety of other things] is not being set, or is being set to nil by something before it's used.
If it worked in 2013 but not in 2015, it's not likely to be just a misspelling of a variable name. But it could be related to some System Variable that's changed, or some command prompt sequence that's different. Or if this is not just a newer version but also on a new computer, it could be something about the computer configuration, or the default template drawing, or something in your setup that's different, such as something that was in an acaddoc.lsp file in the 2013 setup but isn't in the 2015 setup.
In a Lisp file of close to 12,000 lines (!), finding a code problem [if that's what it is] is a tall order. But you should be able to test-run it in the VLIDE [others can help you with doing that far better than I]. Or can you break it apart into some smaller pieces and try them separately, to narrow it down?
BUT one thing I noticed in a quick peruse only up very near the top is that you have a lot of (getkword) functions, with checks on whether what they return is "" [obviously intended to check for the User hitting Enter]. That check works to find whether the User hit Enter in response to a (getstring) function, but when you hit Enter in response to (getkword), it returns nil, not "". It's possible that is the problem -- it may be trying to use a variable that will contain a text string if you give it one of the options, but will be nil if you hit Enter. Try running it without accepting a default value for anything, always specifying one of the options even if it's the one being offered as a default, and see whether it works. If so, you'll need to plow through and fix all those situations to work right with Enter to accept defaults.
Kent Cooper, AIA 