topic Re: LispFunction in .NET Forum

LispFunction

bahman.jf.68 — Tue, 05 Sep 2023 13:55:50 GMT

Hello everyone,

I have a problem with passing a polyline to C# .Net.

I wrote .Net codes to get an object from Lisp and then calculating Area and also get bounding box of the object, but Autocad crashs after selecting a closed polyline. (I will appreciate anyone who corrects codes and adding bounding box method to it)

(setq ent (car (entsel))) (mylispfunc ent)

[LispFunction("MyLispFunc")] public ResultBuffer mylispfunc(ResultBuffer resBuf) { Document doc = Application.DocumentManager.MdiActiveDocument; Editor ed = doc.Editor; Database db = doc.Database; Document acDoc = Application.DocumentManager.MdiActiveDocument; Database acCurDb = acDoc.Database; ResultBuffer rbfResult = default(ResultBuffer); var args = resBuf.AsArray(); ObjectId co = (ObjectId)((TypedValue)(args.GetValue(0))).Value; using (Transaction tr = db.TransactionManager.StartTransaction()) { Polyline lwp = tr.GetObject(co, OpenMode.ForRead) as Polyline; double arr = lwp.Area; tr.Commit(); }

Re: LispFunction

ActivistInvestor — Wed, 06 Sep 2023 03:47:58 GMT

Have you tried stepping through your code in the debugger to find out what is going on?

Also, crash is a vague description. What exactly does AutoCAD do? Does it show an error of some kind? Let this not be a guessing game.

Re: LispFunction

bahman.jf.68 — Thu, 07 Sep 2023 17:48:37 GMT

Yes, the error is to this line :

  double arr = lwp.Area;

Re: LispFunction

norman.yuan — Thu, 07 Sep 2023 18:21:16 GMT

Since you have this line of code:

Polyline lwp = tr.GetObject(co, OpenMode.ForRead) as Polyline;

So, if the opened DBObject by the Transaction is not a Polyline, the variable "lwp" would be points to null, thus the next line will raise error.

You should test like this:

Polyline lwp=tr.GetObject(co, OpenMode.ForRead) as Polyline;

if (lwp != null)

{

double arr = lwp.Area;

}

else

{

// you may want to raise/throw an invalid argumentException to indicate the selected entity is not a Polyline, for the calling lisp code to handle.

}

Re: LispFunction

ActivistInvestor — Thu, 07 Sep 2023 18:56:21 GMT

You do not mention what specific error it is. If as suggested by another reply the object is not a polyline then it will be a null reference exception. If the object is a polyline then it could be something else.

My standard advice on polyline area has always been to use COM to get the area because the managed Curve.Area property can produce incorrect results with closed, self-intersecting polylines.

Re: LispFunction

BlackBox_ — Thu, 07 Sep 2023 19:02:17 GMT

@norman.yuan -

Why instantiate the overhead of a Transaction to test for the correct entity type?

Wouldn't it be more efficient to instead simply test the ObjectId for co.ObjectClass.Name first, if it passes, then use the Transaction?

Re: LispFunction

norman.yuan — Thu, 07 Sep 2023 19:20:48 GMT

@BlackBox_ : I simply pointed out the direct reason of the error OP gets.

If the LISP function does required Polyline, not other curves (Arc, Circle...) as input, then I am with you: I'd first test ObjectId.ObjectClass.Name/ObjectId.ObjectClass.DxfName to make sure it is Polyline before starting a Transaction

Re: LispFunction

bahman.jf.68 — Thu, 07 Sep 2023 20:54:02 GMT

Thank you everyone for replying.

The problem resolved with this line :

if (lwp != null)

{

double arr = lwp.Area;

}

@ActivistInvestor Thanks for your advice, I dont have more exprience with COM programming, I'm good at AutoLisp and I have been working with C# Pure .Net for about one year. Also I think Pure .Net is so quicker than Com or Lisp.

But regarding intersection errors, I think all Lisp, vba, C# returns incorrect result.