Joe_Carrick

Try using the "All ON" Layer Set.

no, no, no - do not copy and paste in the plan. Send to Layout is OK but if you copy and paste in the plan then you will have 2 identical schedules and 2 labels.

Expand "CAD Details" Select and open "Window Schedule" Turn on the "Schedules" Layer It's there just like Chopsaw said.

Nothing. The macro just has to be assigned to the Label of a Layout Box. Of course you need to create the macro - name it builder_plan_name

OK, it's now finished and ready for Prime-Time. See https://chieftalk.chiefarchitect.com/topic/23944-site-area-analysis-macro-system/

It might work as just a one line macro. I'm not sure because sometimes Ruby doesn't like too many methods on a single line. IAE you can try it: result = referenced_full_filename.rpartition("_Builders/")[2].rpartition("/")[0]

I now have my new X11 Site Area Analysis completed. The price for this System is $125.00 - payable into my PayPal Account joe.carrick@dslextreme.com A complete description follows: SITE AREA ANALYSIS MACRO PACKAGE Created by Joseph P. Carrick October 13, 2019 This macro package uses a single macro %site_Areas% placed in the Label of any Chief Architect Object that has the area attribute. Normally that will be a closed Polyline, Polyline Solid, Slab or a Terrain Feature such as a Driveway or Sidewalk. There are several aspects of the Object that are taken into account in how the data is used: Layer - generally names and Labels the area Line Styles – property and setback are automatically recognized Line Styles -- new, existing and demo are also automatically recognized - the Polyline will be labeled as “(N)”, “(E)”, “(D)” Floor Level (referenced floors) are automatically recognized for any building Layers Names containing "Building", "Home", "Structure", "Residence", "Garage", "Storage", "Shed" are automatically recognized as BUILDINGS. Layers Names containing "Building", "Home", "Residence" are automatically recognized as HABITABLE Layers Names containing "Roof", "Slab", "Walk", "Driveway", "Water", "Concrete" are recognized as IMPERMEABLE. Layers Names containing "terrain" will be analyzed according to their material for Impermeable recognition. Layer “(O)” is recognized as an overlapping area of the Impermeable areas and subtracted from the total Impermeable areas. If a Layer Name contains “(N)”, “(E)”, “(D)” they are recognized as NEW, EXISTING & DEMO respectively. There can be only one Property Line and one Setback Line. The same Layer can be used for more than one object. The system will keep track of them as different areas The same Layer can be used on different floors and if the floor is displayed as a “Reference Floor” the areas will be included. The following macros are included to list, calculate & display the accumulated data: %site_Areas_FAR% - displays the Floor Area Ratio %site_Areas_List% - displays the list of all areas %site_Areas_List_Demo% - displays the list of all Demo areas %site_Areas_List_Existing% - displays the list of all Existing areas %site_Areas_List_Ground_Floor% - displays the list of all 1st Floor areas %site_Areas_List_Habitable% - displays the list of all Habitable areas %site_Areas_List_Impermeable% - displays the list of all Impermeable areas %site_Areas_List_New% - displays the list of all New areas %site_Areas_List_Coverage% - displays the lot coverage calculations %site_Areas_total_New_plus_Existing - displays the total of New and Existing All of the above macros are contained in a Library Object named “SITE AREA ANALYSIS RTB” which when placed in a Plan will add all the macros into the plan. There are also Annosets and Layer Sets that can be imported to make setup easier. These have been provided to use with Imperial Units but can be the basis for Metric versions. The macros are designed to recognize which system is in use and use the appropriate units in the data display. Whenever something is changed in the plan, the data in the RTB should be updated automatically. However, this might not always happen so it's important to press and hold the F5 key for a couple of seconds to insure the data is correct. This must be done before printing a Layout.

Build Wall Framing?

Sure, but a better method would be to use: result = referenced_full_filename.rpartition("_Builders/") result = result[2].rpartition("/") result = result[0] This way you only have to know that you want to eliminate everything up-to and including "_Builders/" and everything after the last "/". Note that I'm using the "/" instead of the "\" because that's what Chief uses in the referenced_full_filename attribute.

The actual characters would be required - or the number of "/" characters - or maybe if you just want to eliminate everything after the last "/". There are several possibilities. The macro can become more complex - actually just longer - depending on what rules you want to follow. Ruby is mostly about manipulating data and performing calculations. This case is basic manipulation of a text string - which is very much just an array of characters.

nstart = 43 nlast = referenced_full_filename.length-1 result = referenced_full_filename[nstart,nlast] result = result.gsub(".plan","") result = result.gsub("/Hardin","") explanation: line 3 sets the result to the characters starting at the 43rd character and ending at the last character line 4 strips all instances of ".plan" from the result line 5 strips all instances of "/Hardin" from the result

I have a macro that will show (in the Ruby Console) all the attributes for any selected object. Here's the list for a typical Layout Box: automatic_label ------------ "Graph Schedule Section/Elevation" ------------------------------------------------------------------------------------ String box_scale ------------------ "1/4 in = 1 ft" ------------------------------------------------------------------------------------------------------- String drawing_group -------------- 1 --------------------------------------------------------------------------------------------------------------------- Integer floor_number --------------- 1 --------------------------------------------------------------------------------------------------------------------- Integer height --------------------- 5.390048486681028 ----------------------------------------------------------------------------------------------------- Float layer ---------------------- arch-d_layout_box_borders --------------------------------------------------------------------------------------------- Symbol layer_line_color ----------- 255 ------------------------------------------------------------------------------------------------------------------- Integer layer_line_style ----------- 0 --------------------------------------------------------------------------------------------------------------------- Integer layer_line_weight ---------- 1 --------------------------------------------------------------------------------------------------------------------- Integer layer_set ------------------ "Arch-D Print" -------------------------------------------------------------------------------------------------------- String layer_text_style ----------- "HIDDEN" -------------------------------------------------------------------------------------------------------------- String line_style ----------------- solid ----------------------------------------------------------------------------------------------------------------- Symbol line_weight ---------------- 1 --------------------------------------------------------------------------------------------------------------------- Integer object_type ---------------- layout_box ------------------------------------------------------------------------------------------------------------ Symbol referenced_filename -------- "Jason Bales Residence - Phase 1" ------------------------------------------------------------------------------------- String referenced_full_filename --- "D:/Dropbox/Chief Architect Projects/X11/Jason Bales Residence - Phase 1/Plan/Jason Bales Residence - Phase 1.plan" --- String referenced_layer_set ------- "All On Set" ---------------------------------------------------------------------------------------------------------- String width ---------------------- 3.6485143922610597 ---------------------------------------------------------------------------------------------------- Float

Note: %file% displays the name of the Layout File, not the Plan file the Layout Box came from. IAE. It's not possible to manipulate the Chief standard Global and Object macros from within a user macro because the underlying data is basically not directly available.

Try this as a custom macro placed in the Layout Box Label: nlen = referenced_full_filename.length-1 referenced_full_filename[43,nlen].gsub(".plan","")

No, but it's fairly simple to do. There are 2 Ruby Attributes of a Layout Box that can be used: referenced_full_filename - same as %file% referenced _filename - just the name of the file that was sent to layout. It would actually be better to know what set of letters you want to eliminate rather than a specific number of characters. For example: d:\Users\username\DesignWork\CAX11\Builders\ where you provide the actual username.

You should probably contact Tech Support. They will be able to walk you thru it, step by step.

Michael, My Footing is 32" wide x 18" high. This is a Slab Footing with a -12" offset. Chief reports the foundation wall length as 440", footing thickness as 32", quantity of concrete in footing as 267264.0 cu.in. 267264 / 32 / 440 = 18.98 This still isn't correct - possibly because the footing itself is actually 24" longer than the stem wall. That would make the footing thickness calculate to 18.08" - close enough. Using the footing rebar length really doesn't work since it's the total - depending on the number of bars which is also not reported. In my case I have 2 #4 bars and the reported length is 936" btw, I tried setting the rebar overlap to 0 and then my rebar length was reported as 872" - which gives a length of 436". The bottom line is that the data available isn't really sufficient to accurately get the height of the footing.

I thought I would try to use the foundation wall's concrete volume, length and width to calculate the thickness. Unfortunately it didn't work. My 18" thick footing calculated to be only 12" thick - which means that CA miscalculates the volume. Evidently a case of inaccurate data reported in one of the attributes. In this case the volume was only 2/3 of what it should have been.

Only the footing width is available - for which Chief uses the name "thickness" of foundation wall. The actual thickness of the footing isn't available for labeling.

Make the column using the cabinet tool. You just have to define the front of the cabinet and check the back and sides to match front. FWIW, I generally do not use PSolids except to create a Symbol. With X11 you can actually select your PSolids and Moldings and convert them to a Symbol - which if you specify it's a Cabinet will then allow electrical outlets to be attached.

Most of the time I use Wall Elevations but for those cases where there's a cathedral ceiling I use a "Section/Elevation View" and add a "Mask" for the things I don't want to see. The "Mask" is just a solid filled rectangular Polyline with a Hole. Inside the Hole is everything I want to see. The hole can be edited to fit the floor, wall & ceiling surfaces.

Bob, You need to crop the pic so that you don't have any white space? It also helps if you only have a square pic. That way the scaling doesn't need to be different for each direction.

You have 2 different Window Schedules that both include the Labels for that floor. This has always been a problem. Just find the extra schedule and delete it.

If you simply put a Text Box in a Room with the %room.name% macro in it (or whatever other text you want) then you can word wrap simply by changing the width of the text box. The text can also be multi-line and formatted as you like. You will probably want to "suppress" the actual Room Label. Another nice feature of using a Text Box is that you can put it outside the Room and connect with an Arrow. The macro will display the data.

FWIW, if the Note Schedule is placed in a "CAD Detail Window" it works correctly. The problem seems to be that at least some Wall Details are reversed "x" direction (ie: x reads right to left instead of left to right)