logo
NOTICE:  This is the new PunchCAD forum. You should have received an email with your new password around August 27, 2014. If you did not, or would like it reset, simply use the Lost Password feature, and enter Answer as the security answer.
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
ZeroLengthCurve  
#1 Posted : Monday, January 27, 2014 1:46:43 PM(UTC)
ZeroLengthCurve

Rank: Senior Member

Joined: 5/15/2008(UTC)
Posts: 991

Thanks: 19 times
Was thanked: 37 time(s) in 25 post(s)
It does not seem possible to collect only one surface area info of a solid.

It is not a big issue when dealing with one type of part or even an array of, say, a plank for a table or joists for a house.

But, if the thickessses vary for parts, and the widths and lengths do, too, it can mess up calculations for, say, paintable areas, wetted surfaces, and so on. If one is covering a wall or a floor with decorative and custom tiles or pieces of something, it is not necessary to have the thicknsses involved. Subtracting areas of sides of irregular pieces would make for a lot of work.

Suggestion: Built into the logic of solids an attribute or feature that is "plane aware". The user could then group or meta-layer assign to an additional layer (but not changing the parts' parent/sensible/adminstrative layers) that can also be used in BOMs. So, if the user lassos or groups slab or built-up solids, and hits the shortcut for surface area, the user could select from notional choices such as these:

-- skyward face
-- earthward face
-- outward face
-- inward face
-- mutually-facing each other faces
-- mutally-away from each other faces
-- toward a specified plane faces
-- away from a specified plane faces

Or whatever Tim or others think is better than what I postit here now.
ZeroLengthCurve  
#2 Posted : Monday, January 27, 2014 2:16:40 PM(UTC)
ZeroLengthCurve

Rank: Senior Member

Joined: 5/15/2008(UTC)
Posts: 991

Thanks: 19 times
Was thanked: 37 time(s) in 25 post(s)
I realize that the underlying surface of most solids can be the one-stop/go-to geometry for obtaining the surface area information, but sometimes the surfaces have to be thrown away to reduce model size. Over time, if the solid is face-matched to some other geomety, it would be unwise to rely on an older or an external file to surface area information.

Also, in terms of database thinking, some things should never be duplicated, such as "derived" values. Each part that is its own entity may need to be counted or ignored, and a summary field existing elsewhere cannot be relied upon as a tally. So, the user would end up checking all over the model and layer trees to ensure nothing is missing from the tally.

Also, if a solid that is developed from a surface has takeoff angles and twists, it can end up having none of its surfaces being of equal surface area to the parent surface.

Maybe, an additional option/feature would be:

-- face tagged with surface-area-count marker

That would enable the designer to specifically, persistently, and readily-apparently she what he/she has got and to what direction the surface area count/tally will be counted.

ZLC
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.