getting 3dSolid Box properties using VBA...

[99garry]

Hello!
The problem is:
When i create a Box, then select it and click right mouse button and select properties menu, the window called Propertoes is displayed. This window have information about the box that is selected such as Length, heigh, width and so on...
So i need to write VB application where i can store this parameters. I need to do this only with Box objects that are free oriented in a ModelSpace.
Thank you for your advices!

[SEANT]

Are you saying you need to store the information at time of the box’s creation?

If so then using BeginCommand and/or EndCommand event handler would probably be effective. The normal user interface for a solids creation could be replaced by a custom version that records the pertinent data.

-OR-

Are you trying to retrieve the dimensions of solids already in a drawing? If the solids are indeed simple boxes box then 3DSolid.PrincipalDirections can be used in conjunction with a .TransformedBy and a .GetBoundingBox to retrieve the box dimensions.

[99garry]

Thank you for reply!
I am trying to retrieve the dimensions of solids that are already in a drawing.

As i understood, your method is...
1. Get 3DSolid.PrincipalDirections to find the orientation of the box in a modelSpace
2. Then 3DSolid.TransformedBy ( and here should be PrincipalDirections that we have found in 1 step)
3. And finaly .GetBoundingBox.
That is the way of solving my problem, but i dont like it. I want to know if there is is a way to get properties of the box right from the properties window that you can view in attachment file.

[SEANT]

I want to know if there is is a way to get properties of the box right from the properties window that you can view in attachment file.

It is certainly logical to think that possible but, oddly enough, it is not (at least not for solids with arbitrary orientations in space). Autodesk did not include a full compliment of properties or methods for the 3DSolid object.

In the case of dealing with regular box solids the process I described, though cumbersome, wouldn’t be too taxing for the coder during design, nor the machine at runtime. If the solid is not so regular, i.e., has undergone Boolean operations, the task becomes considerably more complex.

I’ve got a VBA sample if you’re interested.

[99garry]

It is certainly logical to think that possible but, oddly enough, it is not (at least not for solids with arbitrary orientations in space). Autodesk did not include a full compliment of properties or methods for the 3DSolid object.

In the case of dealing with regular box solids the process I described, though cumbersome, wouldn’t be too taxing for the coder during design, nor the machine at runtime. If the solid is not so regular, i.e., has undergone Boolean operations, the task becomes considerably more complex.

I’ve got a VBA sample if you’re interested.

Yes please poste the VBA sample here, or send me email

Autodesk did not include a full compliment of properties or methods for the 3DSolid object. ---------- This is very strange. Because methods and properties like:

MomentOfInertia

PrincipalMoments

ProductOfInertia

RadiiOfGyration

Volume

-- at least requires object length heigh and width for a BOX objects.

I am trying to say that length heigh and width properties are more important than those i have mentioned before.

[SEANT]

The more cynical explanation would be that the 3DSolid portion of the API was purposely hamstrung to obstruct customization efforts competing directly with Autodesk Inventor.

Be that as it may, a lot of things are possible, just with a bit more effort from the coder. I’ll put together that sample and post it shortly.

[SEANT]

Here is a sample.

[patrickpublic67]

Hello SEANT,
thank you for your code, y use it, but there is a problem with boxes who have two same dimensions (example : Long 1000 ; larg 200 ; height 200).
In this example, the dimensions are calculate too long.

Have you a solution/correction for this little problem ?

Sorry for my bad english, y am french..

Patick.

[SEANT]

Interesting. There is a discrepancy in how AutoCAD generates a solid’s Principal Directions. That discrepancy causes my routine to fail on a solid with matching dimensions unless the sides are aligned to X, Y, or Z.

Give me a bit of time and I’ll fix it.

[SEANT]

Here is an updated version that should return the correct dimensions regardless of how length, width, and depth relate to each other.