This isn't going to go away, Autodesk

[Anonymous]

What's it gonna take for us to get a
clearly illustrated API for Mechanical Desktop??? You can't swing a dead cat
by it's tail without knocking over an A2K VBA reference. Yet all FOUR of the
APIs in MDT are poorly demonstrated. The BrepAuto library, which you are
forced to use when you want to create placed features, has ONE example
showing how to create a surface mesh. Hardly helpful.

There seems to be no direct link between parts and the BOM. The
AddAttributes example shown in the McadAuto library adds attributes that
won't list in the BOM, BOM properties dialog or even at the command line
with AMLISTPART! Now what good is that?

The GeAuto library has ZERO examples. In light of the fact that you MUST use
GeAuto to do something as simple as add a dimension to a profile, I would
think explanations are in order.

Let me offer my less-than-fully-informed opinion: Autodesk is intentionally
stonewalling VBA development in MDT. As for the why of it, pick your poison.
The most likely possibilities are: Autodesk can't explain the MDT API
because they aren't familiar with it themselves OR Autodesk is protecting
their strategic partnerships with the established add-on software houses. I
think it's the latter personally. After all, why would I go out and BUY a
sheetmetal app if I could write one? Whatever the case may be, I think it's
time for all the MDT (we would like to be but can't find the stinking
documentation) VBA developers to start calling Autodesk out on to the carpet
and start giving us the same support they bestow upon the A2K developers!

[Anonymous]

You forgot one - How about "The respective talents behind the technology you
refer to are no longer at Autodesk"?

__________________________________

Michael Puckett
programmer@cadvision.com
> Not < an Autodesk hall monitor.
Imagination makes all things possible.
__________________________________

Frank Oquendo wrote in message
news:81gusj$8qp10@adesknews2.autodesk.com...
What's it gonna take for us to get a
clearly illustrated API for Mechanical Desktop??? You can't swing a dead cat
by it's tail without knocking over an A2K VBA reference. Yet all FOUR of the
APIs in MDT are poorly demonstrated. The BrepAuto library, which you are
forced to use when you want to create placed features, has ONE example
showing how to create a surface mesh. Hardly helpful.

There seems to be no direct link between parts and the BOM. The
AddAttributes example shown in the McadAuto library adds attributes that
won't list in the BOM, BOM properties dialog or even at the command line
with AMLISTPART! Now what good is that?

The GeAuto library has ZERO examples. In light of the fact that you MUST use
GeAuto to do something as simple as add a dimension to a profile, I would
think explanations are in order.

Let me offer my less-than-fully-informed opinion: Autodesk is intentionally
stonewalling VBA development in MDT. As for the why of it, pick your poison.
The most likely possibilities are: Autodesk can't explain the MDT API
because they aren't familiar with it themselves OR Autodesk is protecting
their strategic partnerships with the established add-on software houses. I
think it's the latter personally. After all, why would I go out and BUY a
sheetmetal app if I could write one? Whatever the case may be, I think it's
time for all the MDT (we would like to be but can't find the stinking
documentation) VBA developers to start calling Autodesk out on to the carpet
and start giving us the same support they bestow upon the A2K developers!

[Anonymous]

Good points Frank & Mike. I have asked the same questions and got
the same answers (nil)
"Frank Oquendo" wrote in message
news:81gusj$8qp10@adesknews2.autodesk.com...
> What's it gonna take for us to get a
> clearly illustrated API for Mechanical Desktop??? You can't swing a dead
cat
> by it's tail without knocking over an A2K VBA reference. Yet all FOUR of
the
> APIs in MDT are poorly demonstrated. The BrepAuto library, which you are
> forced to use when you want to create placed features, has ONE example
> showing how to create a surface mesh. Hardly helpful.
>
> There seems to be no direct link between parts and the BOM. The
> AddAttributes example shown in the McadAuto library adds attributes that
> won't list in the BOM, BOM properties dialog or even at the command line
> with AMLISTPART! Now what good is that?
>
> The GeAuto library has ZERO examples. In light of the fact that you MUST
use
> GeAuto to do something as simple as add a dimension to a profile, I would
> think explanations are in order.
>
> Let me offer my less-than-fully-informed opinion: Autodesk is
intentionally
> stonewalling VBA development in MDT. As for the why of it, pick your
poison.
> The most likely possibilities are: Autodesk can't explain the MDT API
> because they aren't familiar with it themselves OR Autodesk is protecting
> their strategic partnerships with the established add-on software houses.
I
> think it's the latter personally. After all, why would I go out and BUY a
> sheetmetal app if I could write one? Whatever the case may be, I think
it's
> time for all the MDT (we would like to be but can't find the stinking
> documentation) VBA developers to start calling Autodesk out on to the
carpet
> and start giving us the same support they bestow upon the A2K developers!
>
>
>
>