There is not an API to convert an AutoCAD object to a Plant 3D pipe support like the PlantPipeSupportConvert command does. You can run the command from your code however. This c# example creates a command that has the user select the pipe and an AutoCAD entity to be used as the support. The location of the support is the mid point of the selected pipe. The Plant 3D API is used to get the length of the pipe from the database and it is used to calculate the mid point. The PlantPipeSuportConvert command takes a point for the pipe. (It uses an an input point monitor to get the pipe at that point).
Below code shows the procedure to remove the user specified vertex of AutoCAD 3d Polyline. Code, first traverse through the vertices of the user selected 3d Polyline and prepares a list of vertexes to be erased.
When an entity that is being overruled is dragged, AutoCAD only creates a shallow copy of it. For this reason, the extension dictionary of the cloned entity is inaccessible from within the overrule class. One way to ensure that we get access to the extension dictionary is to drag the original entity and not its clone using the "TransformOverrule::CloneMeForDragging" and return false. Using this technique is not suggested as it is only meant for use with complex entities that can cause performance issues when cloned for dragging purposes.
The workaround is to override the "TransformOverrule::CloneMeForDragging" and continue to return "true" and use the original entity which is a parameter to this method to access the extension dictionary.
We are pleased to announce a significant enhancement to our Autodesk
Developer Network (ADN) Support service. Apart from asking questions privately
through DevHelp Online, you can now also ask your questions on the Autodesk Discussion
Group (Autodesk Forums). Here is the API forums list that integrated
with the DevHelp Online.
Many ADN partners already make extensive use of the Autodesk discussion forums – asking
API questions on the forums as well as through DevHelp Online in order to
benefit from the advice of as wide a range of experts as possible. But there is
a problem with relying solely on a public forum for support - sometimes you
don’t get an answer to your question. We’re fixing that problem by creating
tighter integration between the Autodesk API forums and DevHelp Online (the ADN
From now on, if you ask a question on one of our managed Autodesk
API public forums, you will benefit from the following enhanced support:
- Members of the ADN DevTech team can identify you as an ADN partner
on the forum and prioritize answering your questions.
- If your question goes unanswered, it is automatically escalated to
DevHelp Online to ensure it receives the attention it deserves.
- If you’re not happy with the answer you’ve received from one of
your peers, you can escalate the question to DevHelp Online yourself.
If you’ve not used the Autodesk discussion forums before, we
encourage you to give them a try. You may be surprised at the breadth and depth
of knowledge freely given by the community. With these enhancements for ADN
Standard and Professional partners, you no longer have to choose between asking
Autodesk or asking your forum peers – now you can ask Autodesk and your forum
peers in the same place.
And while you’re visiting the forum, why not browse around and
contribute to some of the discussions.
Taking advantage of this
new service is really easy. The account you already use to login to DevHelp
Online will also allow you to login to the Autodesk forums. If you are an ADN
member, please visit the ADN extranet for more
detailed information on how to setup your forum account so that you are
correctly recognized as an ADN member and benefit from this enhanced support.
If you're an ADN member, if you've been to Autodesk University, if
you use the Autodesk forums, or if you follow this blog then you will undoubtedly know Fenton Webb. That is why I'm writing a post here to announce that - after 13 years serving the AutoCAD developer community - Fenton is moving on to pastures new.
I'm very sad to lose a colleague who joined the ADN team in the same year as I did, but I'm happy for Fenton that he's found a position with another team at Autodesk where he can work on something new and challenging. Fenton has moved to our installer and licensing team - a team he's been working very closely with over the last two years as part of his work on the Autodesk Exchange store (creating the installer template we use for apps on Autodesk Exchange, as well as the internal tools we use to automate the installer creation process for those apps). Fenton will be working on some top secret projects that I'm not allowed to talk about on this blog.
On behalf of the ADN team and (if I may be so bold) AutoCAD plug-in developers everywhere, I'd like to thank Fenton for his hard work and imagination in serving the AutoCAD developer community over the last 13 years. Hopefully, once he's settled into his new position, he'll be able to continue blogging on this site again, and he will be helping us out at AU with several classes in the Developer track and at our DevLab workshop. Bon chance et au revoir Fenton.
Recently a developer reported this error message when a custom .arx module that made BRep calls was being loaded at startup : "'xxx.arx cannot find a
procedure that it needs.”
A way to narrow down the procedure that is not being found is to use gflags.exe that is part the debugging tools for Windows from the Windows SDK. Here are the steps :
1) Run the gflags.exe and specify the OEM product name.
2) Hit the Tab key and turn on the loader snaps
3) Run the OEM product under the Visual Studio debugger until the error message appears in the command prompt.
4) Look at the messages in the Visual Studio output window to identify the procedure name that is not being found similar to the one shown here :
LdrpSnapThunk - ERROR: Procedure "?isSelfIntersecting@AcGeImpCurve3d@@UEBAHPEAVAcGeSelfIntersectTestCallback@@AEBVAcGeTol@@@Z" could not be located in DLL "AcGe19.dll"
First-chance exception at 0x77350108 in TTGCAD.exe: 0xC0000139: Entry Point Not Found.
In this case a method in the "AcGe19.dll" was not being found. Copying
"AcGe19.dll" from the OEM installer folder under
"\x64\aoem\Program Files\Root\acge19.dll" to the OEM 2013 folder
and rebuilding the product resolved the issue.