The same applies for any bugs you find in the SDK samples (and if you'd care to summarize to me how the samples are outdated).
On a related note, I agree that the reference guide should do a good job of describing the basic contract for the API. But the days are gone when relatively static SDK and developer guiide samples are the only place people expect to look for code usage information. (Surely people only ever looked there because they couldn't find the information anywhere else)? The first places I (and, I suspect, everyone else on this forum) look for API examples and advice are: blogs (like Through the Interface or DevBlog), forums (like TheSwamp or the Autodesk forums), and websites (like the Autodesk Developer Center or StackOverflow) - or (more generally) we use Google, Bing or whatever is our search engine of choice.
I can only speak for my DevTech team within Autodesk - but this is why we have started (and will continue) to devote a lot of time to putting as much content as we can in the public domain - but (bugs aside) I'm not planning that we'll be retrofitting any information we post to the DevBlogs into the SDK documentation because to do so would be an expensive/inefficient use of people who could instead be creating much more content on our blogs, developer centers and forums.
HTH,
Stephen
And just to reiterate my offer - If someone is interested in sending me a list of documentation omissions and bugs (ideally in order of priority), then I'm very happy to pass it on for you.
Thanks Stephen and Fenton for your input, and appreciate you guys doing what you can help, other than being able take 6+ months for each ADN support request that comes in to produce lacking documentation I am not sure what else you guys could do.
The DevBlog is helpful and appreciate it.
I am not sure but unless you guys decide how much resources will be put or spent for producing documentation then it is what it is but I would think the best thing to do is spend it on most common scenarios.
I use the docs, but for a particular class or feature unless it directly maps or exposes everything in ObjectARX then there is alot of guesswork, and for common ones you end up spending time in reflector and testing to figure out what is going on.
That comment link has never worked for me but I just tried and it worked.
Is that the best way to get more resources if everyone just started loading you guys up with comments?