topic Re: Error message in .NET Forum

Error message

k005 — Wed, 07 Sep 2022 12:21:06 GMT

Hello everyone

How can I get the error message when the command does not work in the below line of code?

Thank you.

private void btnYap_Click(object sender, EventArgs e) { this.Hide(); Adoc.SendStringToExecute("elev1_symbol\n", true, false, true); this.Close(); }

Re: Error message

_gile — Wed, 07 Sep 2022 13:17:41 GMT

Hi,

See this topic.

Re: Error message

k005 — Wed, 07 Sep 2022 13:21:59 GMT

I added the try-catch structure before posting on the forum. I also put a message box.
It didn't show the message when I tested it.

Re: Error message

k005 — Thu, 08 Sep 2022 18:00:52 GMT

@_gile

elev1_symbol

this is a lisp command. It works from within the lisp routine.

I don't know if it makes a difference... in this case, how should the example try catch structure be?

Thank you.

Re: Error message

_gile — Thu, 08 Sep 2022 19:54:57 GMT

Is there any error message in the AutoCAD command line/text screen?

Re: Error message

hippe013 — Thu, 08 Sep 2022 19:57:45 GMT

(defun myLispFoo () (princ "\nHello World") (princ) )

aDoc.SendStringToExecute("(myLispFoo) ", True, False, True)

Notice the parentheses before and after function name and then a space after that.

Re: Error message

k005 — Fri, 09 Sep 2022 05:51:41 GMT

command line message: Unknown command "elev1_symbol". Press F1 for help.

The classic answer of autocad. In fact, it is clear from this message. but I will specify the lisp name with the

messagebox...

Re: Error message

k005 — Fri, 09 Sep 2022 06:00:02 GMT

i did it this way. but I didn't get the message.

private void btnOfsetAt_Click(object sender, EventArgs e) { this.Hide(); try { Adoc.SendStringToExecute("(elev1_symbol) ", true, false, true); } catch (Exception) { //throw; MessageBox.Show("abcdef lispi yüklü değil."); } this.Close(); }

Re: Error message

hippe013 — Fri, 09 Sep 2022 13:58:08 GMT

Were you expecting an error?

Re: Error message

k005 — Fri, 09 Sep 2022 14:03:57 GMT

Yes. As I mentioned in my question.

so the elev1_symbol command is not available... so I should get an error.

Re: Error message

hippe013 — Fri, 09 Sep 2022 14:04:21 GMT

(defun c:myLispCmd () (princ "\nHello Command!") (princ) )

aDoc.SendStringToExecute("(c:myLispCmd) ", True, False, True)

(defun myLispFoo () (princ "\nHello Function!") (princ) )

aDoc.SendStringToExecute("(myLispFoo) ", True, False, True)

Re: Error message

hippe013 — Fri, 09 Sep 2022 14:07:22 GMT

An error in the execution of the lisp will not bubble up to be an error in the execution of the .NET portion of your code. The try catch will catch errors in your SendStringToExecute and not an error within the lisp itself. That is my understanding anyways.

Re: Error message

k005 — Fri, 09 Sep 2022 14:39:12 GMT

I understand.

I cannot use the try catch construct for this situation.

Thank you.

Re: Error message

hippe013 — Fri, 09 Sep 2022 14:46:06 GMT

If you are trying to catch the error within your lisp, use the *error* definition to catch the error. I was showing how send the lisp using the SendStringToExcecute method. What did you want the Try-Catch to catch?

Re: Error message

k005 — Fri, 09 Sep 2022 15:25:21 GMT

now on this i'm not talking about coding an error message in lisp.

only lisp relation should be in button click event. which, if lisp already exists, the command works. If not, it gives an

error on the command line. not found etc...

I wanted to receive the not found message with the message box.

Re: Error message

hippe013 — Fri, 09 Sep 2022 15:41:05 GMT

How about creating a .NET lisp function that checks for the existence of the defined lisp command and returns a boolean?

Re: Error message

norman.yuan — Fri, 09 Sep 2022 16:09:40 GMT

If you are using SendStringToExecute(), regardless of the code being executed is LISP command or .NET command, there is no use to wrap it with try...catch..., because the SendStringToExecute() is async and only runs AFTER the calling routine ends (in your case, the execution runs through the try...catch... and the button click routine is done, then the action called in SendStringToExecute() starts). So even there is error because of the SendStringToExecute(), the error cannot be send back to the calling routine, because it HAS ALREADY ENDED.

Re: Error message

k005 — Fri, 09 Sep 2022 17:08:12 GMT

Many thanks for the detailed explanation.

I'm closing the issue.