brudgers

If you didn't know it was a workaround going in, I can understand your surprise at its uselessness. Otherwise, I can't. At least it's easier to create something useless.

How about create a roof object with the slope you want... place in class1 Group it. Duplicate it in place. Convert the duplicate to 3d ploy's and place in class2 Mirror it in front view. Now you have an inverted copy of the roof object. You can recreate the inverted copy from the initial roof object fairly easily since both a positive slope roof and a negative slope roof look the same in plan.

Well, I've always found creating .dwg's to be a time consuming process...or one where people get what they get because it's the fastest way to produce the drawings. The other option is just to open your .dwg's in autocad and bind the x'refs. You can do this with a startup script and specifying it in the command line.

I don't think so based on the limitations of Generic Solids under the old (2008) modeler. Under parsolid, it may be different. The attached file shows a loft with the solid option selected. The contents of the solid addition were cut, pasted and grouped. then individually colored/textured. I don't know how it compares to the same process using parsolid.

SP5 released per the list-serve.

Does 2010 create the loft as a NURBS? 2008 does. I thought it was a conversion issue.

Layer links? I know you could do it with DLVP's to keep everything orthogonal and avoid potential glitches with rotate plan.

A quick note. Using the file saved as 2008, the resulting loft is a generic solid. However, a loft using the technique creates a solid addition consisting of nurbs surfaces (or a group of nurbs surfaces if "solid" is not selected when generating the loft). And of course...make sure your profiles are NURBS.

Not quite. A solid intersection would be cleaner - two objects v. three. But the 3d engine in 2008 won't handle the complexity. Maybe parasolids and the root-n-toot-n new stair can.

Given the problems with OSX's help indexer, those who have to develop commercial applications for the MAC don't have many options...never mind those unfortunate few who have to find something dual platform - like NNA. What puzzles me about this thread though, is why Mac users are relying on help in the first place. Apparently they don't brew the Cupertino Kool-Aid like they used to.

Don't know about 12.5 but in 2008 you can choose between exporting classes or layers to autocad layers.

Print it like a newspaper. Roll the manuals up and stick them in a plan rack.

Releasing the manual with an open license that allows bulk printing by third parties wouldn't cost NNA squat and would help users.

I've read there is a limit on image size.

I think once you actually price that option out, you will find it to be less than cost effective.

Maybe NNA could provide non-exclusive copyright permission to print the manuals in bulk and sell them to interested persons. It would save wasteful printing, and provide what some customers deem necessary. The logistics for NNA would be minimal and it would not impact an existing revenue stream.

stair with two subtractions

At least as much as you have.

What's the story on DoMenuTextByName ('extrude',0); ??

Better it be beyond my current technical skills to help Bruce than beyond my character.

the profile may be wrong too. It's a demonstration of the modeling technique. So draw the 2d plan view. Compose it as as a polygon. Copy it to the clipboard Edit the solid intersection. Edit the topview solid extrude. Paste the new polygon from the clipboard. Delete the old polygon. Exit editing the extrude. Exit editing the solid intersection.

Modify as in wrapping it with additional functionality. That's sort of the idea behind scripting. Begin [getclass of existing object to be extruded] [run extrude command] [change class of new extrude] End The VSextrude functions look lovely. But implementing them with something like the familiar interface is more complex than just calling DoMenuTextByName. At some point, I'll probably take another crack at it. But I stand by my assertion that not being able to call extrude from the menu is stupid. The fact that the documentation is just plain wrong, however, is pure Kool-Aid.

Here's how I would model this sort of stair. You can fairly easily modify the solids for the stair profile and the plan view.

The Palladio Software can do it. Just ask the late Frank Pepper.

I was trying to write a quick and dirty script to help Bruce. Per the documentation, "extrude" should be callable by DoMenuTextByName. But it isn't. Yes, there are workarounds. The goal was to modify the existing and familiar command to fit Bruce's workflow. Not to reinvent it.