Joe_Carrick

There are some in the Library. Type "shutters" in the search box.

I suspect that someone gave you negative reputation points for checking your own answer as the "Best Answer". That's generally bad form and some people might object. If you get too many negative reputation points you could get blocked. Most people think the reputation points are silly - but others like to reward good contributions by giving a positive point. It's kind of like paying for help - but it doesn't really cost anything.

Better yet, Open the "Deck/Porch" Room and in the Wall Materials Panel check the box that says "Use Default Material". This is a common problem when using "Paint".

Open the "Deck/Porch" Room and change the Wall Material to your Siding Material.

Here's my solution: 1. Draw a line right over the offending module line. 2. Open that line's dbx (dbl-click) 3. Select Color, Eyedropper, click on the Countertop Fill. You still get the outer edge of the Cabinets and the edge of the Counter Top.

Not gonna happen! The only reason I am not on X10 is that I don't know what it's going to be called. X10, XX, XArch_1,.... ??? Based on my family history I figure I've got at least 25 more years. I could be using Chief Version XL3 by then. Hmm., sounds like a BMW. xx

Spacing is not automatic. Unfortunately the attribute for spacing is not available to Ruby. You need to add that in the RTB after the %Framing Member(s)% yourself. ie: %Framing Member(s)% @ 16" o.c.. or whatever your spacing is.

Rich, You could copy the content and paste it in a PDF and add an index and bookmarks. Then put a shortcut on the Desktop to the PDF. Just a little food for thought.

Mick, RTB is abbreviation for "Rich Text Box".

I think the KEY POINT that Gerry made is that not only do we need the Polylines to have Labels but that they also need to have unique identifiers (aka Names). This should also be done for the Terrain Features such as Roads, Terrain Paths, Driveways, etc. Another item that would be really helpful would be a floor_number for Rooms. I am currently using a couple of different methods to identify the floor a room is on but neither of these is 100% fool proof. Gerry's other points regarding persistence of data, grouping & execution of a sequence of macros on demand are also valid. I will say that I can already perform a sequence of macros on demand very easily - but it would be nice to be able to assign those to a Toolbar Button. The Tables can be done by having them stored as Rich Text Boxes in CAD Detail Windows.

Select the Cabinet, then hit the Tab key. That will select the sink - or any other item that has been inserted into the cabinet such as an appliance.

Now that's funny! Thanks Dermot - made my day.

Such as?

How about a PLine with Fill? Line Style = blank, Fill Color = same as counter top. IOW, a Cad mask.

Scott, I agree that PLines with Labels are needed. My main concern with PLines is that they do not automatically adjust when the building and site features change. That means the user has to manually adjust the PLines to match those other items. I'm trying to get a more reliable method - one that is always in sync with the Plan. Terrain Features such as Driveways, Sidewalks, Roads, etc should also have Labels. All these things are potentially needed for such calculations. Rooms - including Courts, Decks, Balconys, Porches, Garages, etc - already have names and types that can be used to accurately calculate building areas. I know that in general you do not like to use Room Types but I'm sure that you do use them for some things. I personally use them because they provide more information.

It appears that the best bet would be to start with the Wikipedia Standard - then add additional macros on a custom basis depending on the local requirements. So maybe I end up with: FAR FAR - San Diego FAR - Anaheim FAR - Riverside FAR - Big Bear Lake LC LC - San Diego LC - Anaheim LC - Riverside LC - Big Bear Lake Each macro customized to meet the needs of that particular local. It's doable - and having a basic starting place makes it easy enough.

I have been working on a macro system that automatically keeps track of all Building Areas by Room, Floor, Room Type, and a variety of other factors. It works invisibly and can calculate the Total Areas, Sub-Totals by Room_Type, FAR and Lot Coverage. I can even go so far as to have it provide sub-totals for the Bedrooms, Master Suite, Baths, etc. In order to have as complete set of macros for FAR and LC I need to know what needs to be included and what should not. I know what the jurisdictions that I do work in require but I also know that they are not all the same. If I have a macro that covers each variation as required by the jurisdictions then anyone could use it to get an automatic display of those things - calculated accurately.

OK, so depending on the jurisdiction there can be a lot of difference in what the Building Dept can require in terms of the FAR and LC calculations. Generally, the FAR is simply the Gross Floor Area (All Floors) / Total Site Area The LC is generally the Total 1st Floor Area of all Structures plus Parking Pads & Driveways / Total Site Area Sometimes a jurisdiction also wants a Main Building Footprint Coverage which includes Deck, Porches, Paved Courts, Sidewalks, etc. What are the most common in your areas and are there any additional items required?

Once it's connected to a Framing Member with an Arrow it will work. It's possible for arrows to get disconnected at either end, so you might want to delete the arrow and add a new one. Options in the Text Box dbx (Add an Arrow)

Scott, Send me a GTM invite and I'll show you directly on-line.

Select the Text DropDown -> Text Macro Management. It's the same tool you would use to define a new macro

This is not a predefined Library CAD object. It's just the Macro itself which you need to insert into your own Text Block.

Scott, You have to "Import" the macro into your Plan using "Text Macro Management". DUH!!!! I suppose Chief should be smart enough to do that when you try to open a .json file but.........

Attached is a macro to Annotate Framing Members. It can be attached to the Label itself or it can be inserted into a Text Box for use with a Reference Arrow. Framing Member(s).zip

OK, I get that to work in an Elevation View (Wall Material Region) but not in Plan (Floor Material Region). But..... It offsets every instance of that Pattern Globally. IOW, if you have 2 Wall Material Regions next to each other and you offset the Pattern in one of them you will see that the Pattern has been of offset the same amount so that they line up. What is happening is that the origin of the Hatch Pattern has been globally moved. All instances of that Hatch Pattern in the View will have been moved. The offset is not relative to the object - it's relative to the 0,0 origin of the Plan. You can of course copy the Material and make offsets for both the Texture and the Pattern - they do not automatically match - but they are both still relative to the Plan Origin, not the object they are assigned to.