Joe_Carrick

No, there are no defaults for Layout Boxes. OTOH, The %scale% macro in a view sent to Layout will display correctly when the Layout is printed.

Refer to "Help" Search Help for the subject. Ask here - but POST THE PLAN

Boy, we all jumped on that in a hurry

Open the Wall dbx and set the Beam Size in the "Rails" panel. There's a drop-down that allows you to edit each rail. The Beam is considered a rail.

There unfortunately no way to get the lengths of individual edges of Roof Planes. We would need to have those lengths and they would need to be broken down by gutters, hips and ridges. Currently, that data isn't available as Ruby attributes.

See Posts #7 & #11 of this thread. I can customize the table(s) to show just what you want. The macro package is $50 and the tables update dynamically. That's the advantage of a "Live" tool. Or you can export the Materials List to Excel and enter whatever formulas you want. But you'll have to do that every time you make a change.

BT, Your macro only returns the area of a single Roof Plane. That's the simple part. Turning it into a set of tables showing all Roof Planes is another story. Here's an example of the output of my "Roof Area Analysis" macro package. There are actually 3 different versions of the table - depending on what columns you want to display. As I said before, the displayed areas in the columns can easily be modified to be displayed as "squares" instead of sq.ft. if that's desired.

If you mean a "Spiral" then I don't think so. I'm pretty sure CA would have already leaked that if it was going to be in X9. btw, To be anyplace close to a legitimate (legal) Spiral Stair, you need a Symbol created specifically for the height and diameter. I've done some in the past on a custom basis. I can do them fairly quickly ($75 per stair)

Michael, %1%%Electrical Notes% %2%%Electrical Notes% etc. %1% ---> $Note = 1 %2% ---> $Note = 2 %Electrical Notes% uses the value of $Notes as an internal parameter to construct the file name. If you really want to use numerical parameters to branch within a macro, this is IMO the simplest way and it doesn't require CA to do anything. You could even use a String value: %Elect_Notes% ---> $Note_Type = "Electrical Notes" %Framing_Notes% ---> $Note_Type = "Framing Notes" %Elect_Notes%%2%%Notes% ---> Filename "Electrical Note.1" constructed %Notes% But we still need a decent Browser interface for macro organization.

That can be done fairly easily but you would essentially need a separate macro for each file and you would need to know the name of the file you want to get the contents you want. It's probably easier just having separate macros with the notes directly in them.

As Michael said, Ruby macros could be inserted into the notes. But they would not show their content in "Pigeonhole" - instead just showing the macro name. But when copied into the Label of an Object, the macro would execute - thereby showing the macro output. OTOH, It's possible to use "Pigeonhole" as a filing system and copy the note into a Ruby macro - or directly into a Label or Text Box. I'm not sure how much advantage there is to either of the above.

Bob has it correct. Forget about it being a "Roof" and just draw the Railing Walls you want. If the "Floor/Roof Edge" needs to extend further out you can draw "Invisible Walls" at that location.

Hi Chris, I often share a simple macro here but for macro packages that are more comprehensive (and take more than an hour to create) I charge a nominal fee. My Roof Area Analysis Macro Package is $50. I can customize it to display the area of each Roof Plane (and the Total Area) in "Squares" instead of "Sq.Ft." If you would like this or any of my other macro packages https://chieftalk.chiefarchitect.com/topic/6595-joes-macro-a-month-subscription-service/ , I can send you a PayPal funds request.

I don't think CA ever gives or removes the points. Other users can give a positive or negative point (the arrows at the bottom right of a post) if they think it deserves one. As long as you are helpful, respectful & positive in what you post it's very unlikely that you will get any negative points. If another user really likes something they will often give a positive point.

3D Moldings can also make a big difference - but 120 windows and probably a lot of walls and doors are also going to slow the display considerably.

Bill, My Graphic Standards is the 5th Edition - (1956) So I would guess the use of the term originated in the field sometime after 1960.

FWIW, I went back and looked at my Graphic Standards and Time-Saver Standards. I did not find any instance of the term "Head Casing". Apparently, this is terminology is akin to the word "ain't" - a construct by those who didn't know the correct name that has become common even though it's inaccurate. It would be really interesting to know at what point in time it first appeared.

Bill, Are you a "Head Case"? Yes, "Head Casing" is used sometimes today - but it's not the most common meaning. "Head Casing" is used much more commonly as the CAP of a Well.

I just love it when the OP solves his own problem.

I just love it when the OP solves his/her problem.

OK, check this:

The Door and Window Dialogs in Chief have a "Lintel" panel. This is not the correct name - it should be called "Architrave". A Lintel is a Structural Beam above an opening - may also be called a "Header" in wood frame construction. An Architrave is the Decorative Cap - originally at the top of a Column but the term has been extended to cover openings as well.

Alex, The dialog you are showing is for the framing. What you want is the "Lintel".

Thanks Ray - but the only way it's going to get fixed is if CA does it. Neither I nor Michael can do anything to make it work better. Let's hope it's done in X9. If not, we just have to keep asking.

In case anyone can't figure out the "code" look carefully at the macro name. ABCDEFGHIJK MNOPQRSTUVWXYZ