Today was my sons 6th birthday and had a bowling party where I spent a decent amount money and had to deal with and entertain 30 other people's creepy little kids so in the mood to rant.
@DiningPhilosopher wrote:I'm still not sure what the person that implemented this method was thinking.
I think the problem is there is no person or person reviewing and testing. I seem to remeber Kean mentioned on his blog that it is automated and done with some tool or program.
What that tells me is there is not much reviewing of what was generated and that no testing was done.
I do not see how they could even sucessfully compile if GetUnreconciledLayers() was called for testing.
This is pure speculation but I do not think it is so much the people responsible for the API that allow this to happen, but for the higher-ups who decide on how much resources will be used for maintaining the API, and with limited resources and a deadline to roll it out they do what they can.
It is acceptable for unuseable methods to make it in the release of the API?
Unuseable is probably not the right word but a method that will not allow you to do a successful build.
I know autodesk was aware of this before 2014 release, and still not fixed.
In the 2013 documentation the signature was
public unsafe void GetUnreconciledLayers(
AcArray<AcDbObjectId,AcArrayMemCopyReallocator<AcDbObjectId>>* modopt(IsImplicitlyDereferenced) idArray
); In 2014 documentation it was changed to
public ObjectIdCollection GetUnreconciledLayers();
Then at bottom in Links section it has 2013 signature as if whoever updated the docs change what the method signature should be and pasted what it really is at bottom.
What is the reason for something like this not being addressed?
From what I understand the when something like this is reported to the ADN team they verify the bug exists and notify the engineering team.
This might be a method that no one ever used and only has been reported a few times, but can you see how it gives the impression your not concerned releasing things like this publicly?
Speaking of layers and from the name of the properties it is obvious what the returned boolen represents, but mainly out of curiousity to see if it would get fixed I have reported for the last 2 years that the description for IsHidden & IsLocked is the description for IsFrozen.
The description for all three is "Assesses if the layer is frozen".
All it would it take is to change frozen to locked for IsLocked,
and frozen to hidden for IsHidden.
I know its minor but it just gives me the feeling you do not care about the quality.
With other APIs I have dealt with when a issue arises it just seems your made to feel they are concerned with the quality and are working on fixing the issue.
You can always go to Autodesk's carrer page to see what they are hiring for and get idea where they are putting the money, and have not looked at it lately but last time I looked it seemed it was for the entertainment side and software that its description seemed to describe 3dMax, Revit, etc....
I just get frustrated sometimes and wish Autodesk would realize if they invested more resources and produced better quality API and documentation that it would attract more developers and allow 3rd party developers to more easily create useful plugins, and would benefit from the 3rd party developers doing the work for them.
Again not blaming or trying to jump on any person but more on Autodesk decisions on resources allocated and procedures for fixing issues with API, or those kids put me in a bad mood.
You can also find your answers @
TheSwamp
