There seems to be several of the same questions asked over and over again. I would like to point out that many of your questions can be answered by reading the documentation and looking at the samples. They can be found here:
Of most interest are the "ObjectARX SDK", the "Help Files", and the "Samples and Labs".
All can be accessed through the link above.
Also if you are new to ARX in general there are several good resources that you can read to find some answers to your questions.
First is the ObjectARX & Dummies, found at:
It is written for Visual C++, but most of the information applies to C# and VB.NET.
Next on "The Code Project" there is a page that describes how you can use a tool called "DOTNETARX" developed by arxbird, to facilitate your Object ARX development. I personally refer to the source code to see how some things are done. That page is located at:
Also, on CADForums, there is information on how you can have your completed .NET ARX DLL loaded when AutoCAD starts up. Look Here:
I would like you to add your "found resources" to this post so the community may benefit as well. Also, don't rule out the Autodesk ARX Discussion group for general ARX information that you may be able to apply to Object ARX as well.
This post is not meant to discourage people from posting questions in this Group, but only to accelerate the knowledge level of all.
I would also suggest that if the documentation fails to answer your question, before you post, search this discussion group, then search the ARX discussion group. Hopefully someone has already asked a similar question that you can apply to what it is you are doing.
>> There seems to be several of the same questions
>> asked over and over again. I would like to point
>> out that many of your questions can be answered
>> by reading the documentation....
Hi. Might I ask what 'documentation' you are referring to?
>> I would also suggest that if the documentation fails
>> to answer your question, before you post, search this
>> discussion group, then search the ARX discussion group.
>> Hopefully someone has already asked a similar question
>> that you can apply to what it is you are doing.
>> This post is not meant to discourage people from
>> posting questions in this Group, but only to accelerate
>> the knowledge level of all.
Your post may not be meant to discourage people from
posting questions, but that's essentially what it does,
and I also don't think that following your suggestions
serves the stated goal of 'accelerating the knowledge
level of all'.
Personally, I think that the fact that questions are asked
here is a good thing. The answers they get are often far
more informative/enlightening than the 'documentation'
as you call it, or the samples.
I also think that asking the same question here more than
once, even if the question has been answered before, is not
necessarily a bad thing. Perhaps for questions like 'how do
I turn osnap off via the keyboard', that may be the case, but
in a newsgroup like this, there are many questions that are
subjective, with no clear; unambiguous; or widely accepted
or agreed-upon answer.
Another problem is that many of the things we discuss here
is 'dated' subject matter, that can change with each release
of AutoCAD and/or .NET and Visual Studio. Hence, answers
to questions, and even the questions themselves, can be
correct and accurate for a certain amount of time, but may
also become 'stale' or inaccurate with a newer release of a
Because of that, and because each time the same question
is answered it can be answered differently, contributing to the
overall knowledge of the subject; showing contrasting points
of view; alternative or newly-discovered ways to achieve an
objective; and take into account changes to the APIs or tools
and technologies involved, that may not have been applicable
in previous answers, and so on, I respectfully disagree with
your ideas about this.
I also think that contrary to what you say, asking questions
here, including ones that have been answered before, serves
to do precisely what you suggest not asking them does, which
in your own words, is 'accelerate the knowledge level of all'.
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
Frankly, I think you should avoid DOTNETARX. The author sometimes posts here, but all the magic workarounds I've seen that the author is always trying to push are just calls to the interop libs that are easier to accomplish without the library.
What are you trying to accomplish with DOTNETARX? Try starting a new thread and I am sure plenty of people would be willing to explain how to accomplish any of the features in the library.