Sorry, can't agree with you.
I think you have formal API documentation confused with
learning/training/educational material.
Given the reality of limited resources to produce either, by diving head
first into advanced topics, you are getting what you asked for. I have seen
plenty of folks achieve good results with the managed API, by first focusing
on the basics of its use before attempting to do advanced development with
it.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009
http://www.acadxtabs.com
Introducing AcadXTabs 2010:
http://www.caddzone.com/acadxtabs/AcadXTabs2010.htm
Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
wrote in message news:6234661@discussion.autodesk.com...
Sorry Tony, but I have to argue that it is a lack of docs. The amount of
documentation for API functions has nothing to do with how skillful I am. If
I searched the API docs, found hits, and was then asking about what it all
meant it would be different. That would mean it's above me and I need to
learn some more first. However, me programming with the AutoCAD API for a
year would not instantly grant me knowledge of the more advanced functions.
There would still have to be documentation saying this function does this,
returns this, and takes these kinds of arguments. I never said the Jigg
concept was painful, i'm saying i have seen no documentation whatsoever that
even mentions what it is.