.NET
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Derive custom objects from AcDb.Entity

5 REPLIES 5
Reply
Message 1 of 6
jbooth
271 Views, 5 Replies

Derive custom objects from AcDb.Entity

Is there any ETA on this from Autodesk? Last I heard, their current stance was to limit custom entities to unmanaged objectarx.

This has been on my wishlist for quite some time. I was only wondering if there were new developments since I asked about it last year.
5 REPLIES 5
Message 2 of 6
Anonymous
in reply to: jbooth

If you cannot do objectArx, doesn't the idea scare you? It scares Autodesk.
I am against the idea of custome ents in .net, even Adesk has not handled its own custome entities in vertical
applications well.


Jason Booth <>
|>Is there any ETA on this from Autodesk? Last I heard, their current stance was to limit custom entities to unmanaged objectarx.
|>
|>This has been on my wishlist for quite some time. I was only wondering if there were new developments since I asked about it last year.
James Maeding
Civil Engineer and Programmer
jmaeding - at - hunsaker - dotcom
Message 3 of 6
jbooth
in reply to: jbooth

You are making the assumption that a choice not to write unmanaged code is due to some fictional fear of ObjectARX.

Thanks though. You really posted something useful. Oh wait...
Message 4 of 6
Anonymous
in reply to: jbooth

I wouldn't expect to see custom objects in managed code anytime soon.

Custom objects rely heavily on C++ and C++ based inheritance, polymorphism, and encapsulation. Those things cannot span langauge/runtime boundaries.

If you want to do it, learn and use native ObjectARX.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009
http://www.acadxtabs.com

wrote in message news:5898670@discussion.autodesk.com...
You are making the assumption that a choice not to write unmanaged code is due to some fictional fear of ObjectARX.

Thanks though. You really posted something useful. Oh wait...
Message 5 of 6
jbooth
in reply to: jbooth

I figured/understood as much. It would be very difficult to write proper wrapper classes for the required unmanaged objects, but if they want to keep migrating into .NET my guess is that they will have to look into it eventually.

My real question here is if Autodesk had any news on this subject, and from what I've seen I would bet the answer is no.

Thankfully my workflow doesn't even need custom entities; adding them would only be a "bonus" to what our software could already do. I have no problem waiting another 1-2 years for new info on this subject.

Thanks.
Message 6 of 6
Anonymous
in reply to: jbooth

Jason:

Autodesk have made it clear that they do not plan to support custom
entities in .NET. I've heard various diplomatic reasons given for this, but
the main reason is that they don't want a proliferation of custom entities
created by untrained programmers. 🙂
--
Owen Wengerd
President, ManuSoft <>
VP Americas, CADLock, Inc. <>

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report

”Boost