Little push up required

[The Buzzard]

You can try adding this after you have set your mode etc. It can help debugging:

 

(defun debughelp ()
  (setq *error* nil)
  (setvar "CMDECHO" 1)
  (trace c:lsd)
  (vl-load-com)
  (vl-bt))
(debughelp)

 

-David

 

David,

 

I placed the code you supplied in Vivians code and got this message. error: Exception occurred 0XE0000001 instead of the other message.

I looked this up and found a similar problem someone else had when they got this message. They also mention that this error would occur after running their program a certain number of times.

 

This is the link to that message I found.

 

http://discussion.autodesk.com/forums/thread.jspa?threadID=319431

[David Bethel]

I agree with Lee. It is difficult to see what the final product is.

 

It looks like you can use (align ... ) after it has been initilized. Using (command "Align".... ) gets you the nested 4 deep error

 

Buzzard, those exception errors drive me nuts. Same with an unwind error. ACAD and Windows just don't get along. -David

[The Buzzard]

I agree with Lee. It is difficult to see what the final product is.

 

It looks like you can use (align ... ) after it has been initilized. Using (command "Align".... ) gets you the nested 4 deep error

 

Buzzard, those exception errors drive me nuts. Same with an unwind error. ACAD and Windows just don't get along. -David

 

 

As I mentioned in post 16, When this line is commented out the error stops.

(command "erase" en "")

 

This would suggest to me that the problem lies somewhere at the begining of the code in the selection set.

 

You will also see the object that is being created.

[Lee Mac]

I agree with Lee. It is difficult to see what the final product is.

 

It looks like you can use (align ... ) after it has been initilized. Using (command "Align".... ) gets you the nested 4 deep error

 

Buzzard, those exception errors drive me nuts. Same with an unwind error. ACAD and Windows just don't get along. -David

 

As I mentioned in post 16, When this line is commented out the error stops.

(command "erase" en "")

This would suggest to me that the problem lies somewhere at the begining of the code in the selection set.

 

You will also see the object that is being created.

 

I think there are a lot of things that are contributing to the errors - but mainly the use of "Align" as it is an EXRXSUB routine (Arx app), which may have changed from version to version.

 

There are a few other things, like the use of "layer" instead of "-layer", causing the dialog to appear unnecessarily.

 

Because of the above, I thought it best to provide Vivian with a foundation for a program, to get him started.

 

Personally, I would avoid "command" calls at all cost (unless absolutely necessary), and especially EXRXSUB's. I have no doubt that the object could be created without use of the Align command, using the right geometry. Although, I found it difficult/didn't have the time to dig through all the points in the original code.

 

As for unwind errors etc, I found they pop up a lot when using the "Coordinate" Property of Polylines, but then not always - and I am yet to find a way around them.

 

Lee

[The Buzzard]

I think there are a lot of things that are contributing to the errors - but mainly the use of "Align" as it is an EXRXSUB routine (Arx app), which may have changed from version to version.

 

There are a few other things, like the use of "layer" instead of "-layer", causing the dialog to appear unnecessarily.

 

Because of the above, I thought it best to provide Vivian with a foundation for a program, to get him started.

 

Personally, I would avoid "command" calls at all cost (unless absolutely necessary), and especially EXRXSUB's. I have no doubt that the object could be created without use of the Align command, using the right geometry. Although, I found it difficult/didn't have the time to dig through all the points in the original code.

 

As for unwind errors etc, I found they pop up a lot when using the "Coordinate" Property of Polylines, but then not always - and I am yet to find a way around them.

 

Lee

 

Lee

 

I took several steps to isolate this error including -layer among some to mention. I also removed variables en & ed from the variable localization and they still come up nil after running the code. At that point there is in fact a problem in the selection set section of the code if these variables have no value and are not localized.

 

If you are going to attribute the problem to multiple command calls, you should really think again about that since there are many program that use that method without error. It maynot be an ideal way to go about programming, But it will run all the same. Some people including myself need to crawl before we can walk in the lisp world. If these methods help people learn then for now, So what?

 

I am not basing an opinion at first glance of the code. I did break it down an narrowed it to that area of the code.

 

I am only trying to be helpful here and not offering an expert opinion, But I have gone through errors such as this on one of my previous codes which was similar in with regard to version issue.

 

I agree this program could have been written another way, But when your learning and you run into a problem, Scraping the whole idea for another is not an answer to the problem. You know me, I like having my space as well when I am set in learning a way that I feel comfortable with.

 

Anyway when I can get some more time I will continue to look. I already mentioned what I had found and if this is useful or not thats OK.

[viviancarvalho]

(command "erase" en "")

 

Actually yes Buzz

It works perfectly fine when i comment out this erase command.

[The Buzzard]

(command "erase" en "")

 

Actually yes Buzz

It works perfectly fine when i comment out this erase command.

 

Viv,

 

Just so you understand, The erase command is not the problem. Its the variable en as well as ed. These are nil after I removed them from the variable localiztion. I think if you spend some time on the selection set portion of the code you will get past this issue. When I commented it out I only bypassed the problem.

[Lee Mac]

I took several steps to isolate this error including -layer among some to mention. I also removed variables en & ed from the variable localization and they still come up nil after running the code. At that point there is in fact a problem in the selection set section of the code if these variables have no value and are not localized.

 

If you are going to attribute the problem to multiple command calls, you should really think again about that since there are many program that use that method without error. It maynot be an ideal way to go about programming, But it will run all the same. Some people including myself need to crawl before we can walk in the lisp world. If these methods help people learn then for now, So what?

 

I am not basing an opinion at first glance of the code. I did break it down an narrowed it to that area of the code.

 

I am only trying to be helpful here and not offering an expert opinion, But I have gone through errors such as this on one of my previous codes which was similar in with regard to version issue.

 

I agree this program could have been written another way, But when your learning and you run into a problem, Scraping the whole idea for another is not an answer to the problem. You know me, I like having my space as well when I am set in learning a way that I feel comfortable with.

 

Anyway when I can get some more time I will continue to look. I already mentioned what I had found and if this is useful or not thats OK.

 

Buzzard,

 

I realise that most, if not all, will need to crawl before they can walk, and I too used to use a ton of command calls (just look at the piping program I made), but I realise that these methods are very unreliable and not to mention slow. It is very easy to rely on command calls as they will get the job done (most of the time), and they use knowledge that the ACAD user is very familiar with, and so I am trying to point Vivian in a better direction as soon as possible, by using entmake. Also, my emphasis was more on using the "Align" command in the program.

 

Lee