Joe_Carrick

Johnny, You can use the %view.name% macro in that label. It will display whatever you have named the Wall Detail in the Project Browser. The attached macro can be used in the Default Wall Label and any new wall will be automatically named with the Floor Number and Wall Number and the Wall Type. Wall Labels.json

Import this macro in TMM (Text Macro Management). Then whenever you select an object you can open TMM and hi-lite _Object Properties to see all of it's attributes and their values. Any of these attributes can be used in a label by simply placing by enclosing the attribute with %.....%. The can also be used in a Text Box with Arrow. In most cases CA has already provided Object Properties to be used in the Label. Custom Macros can be written using the attributes as well. If the custom macro begins with: referenced ? obj= referenced : obj=owner then you can simply place obj. in front of the attribute and it will work either in a label or in a Text Box with Arrow. _Object Properties.json

You can open the Door or Window dbx and specify the number of trimmers, but there isn't any per width settings for the number of trimmers.

Attached are a couple of macros that can be inserted in one of the OIP fields to be used in Door and Window Schedules in lieu of Chief's "Header" column. There's no charge for these. Header Labels, OIP Fields.json

CJ, Use a Wall Niche and then move the Panel into that location.

You should ask your questions in the Q&A Forum. Tips and Techniques is for people to post Tips, not for questions. Some users will not answer questions posted in this Forum.

Notice the date that I posted that - October 17, 2014

Sorry, CA has not yet figured out how to give us this functionality.

Michael, Don't move the library or any other individual files. Move the entire Data Folder and set the Path to the Data Folder in Preferences. Then it works fine - no problem.

We don't put the files on the cloud. We just put them in a folder (dropbox) on the local drive. Dropbox then syncs to the cloud and dropbox folders on our other computers.

I use Dropbox for both Plans and the entire Chief Data Folder. This is not a problem as long as you have the paths set correctly in Chief to your local Dropbox Folder.

These are more generic than not. If I need a new detail for a specific project I will either create a new one from scratch or copy/modify and existing detail. I use Chief's OOB "CAD Block Template" as the basis for each of my "Detail Plans" and as I create and modify details I add them the "Named CAD Detail Windows". I have a set of these "Detail Plans" for different types of details. The "1st Floor Plan" is where I create and modify details which I then copy to CAD Detail Windows. I don't rely on Sections very much as the basis of Details and I don't rely on them being "live". IMO Chief basically creates accurate Sections - but not 100% correct. I prefer to create the Details myself. For full Wall Sections I do use portions of Live Camera Section views.

I use individual CAD Details sent to layout from CAD Detail Windows in my "Detail Plans". Since these details are not "Full Sections" there's no noticeable "slow down" of the Layout.

You think he might need to save some of those brain cells?

How many brain cells does it take to make a mouse click? I bet it's less than what it takes to use a hotkey

Ed, You need to make this request in Suggestions

The original Chief Plan probably has things in it that the Architect doesn't want to give away. (Symbols, Macros, etc). While you can import the DXF into your own Chief Plan, it will not be the same as the original Chief Plan. The DXF simply doesn't contain all the Chief Plan intelligence.

There are basically 2 ways to accomplish that: Use Custom Countertops and put them on a separate layer Use a Layer Set where the Cabinets are displayed as a "blank linestyle" and maybe set the Cabinet Layer to "locked"

Scott, Those things in the layout box dbx are not the same as what the macros are referring to. There are currently no attributes or macros to get that information into a label. Unless CA adds that data to the Layout Box attributes it simply isn't possible. Even in the Plan only the floor_number is available. None of the "reference" data is available as attributes.

Scott, The "Referenced" attributes in Layout Boxes are not the same as in a Plan. They "REFER" to the Plan from which they came. %referenced_full_filename% ...... The full file name of the "Plan File" that layout box came from %referenced_filename%.............. The "Plan File" name without the path %referenced_layer_set% ............ The Layer Set in the Plan If the layer set is changed in the Layout Box they when you double click on the layout box it will open the view in the Plan with that Layer Set active. It will not change the Annoset. There is a new attribute %floor_number% for all objects. This is available in the Plan but in Layout the value is always 1. If you select a layout box and open the Ruby Console, then type "owner.names" you will find a list of all the attributes for that object. These attributes values can be displayed in the label by placing a "%" before and after or they can be used in User Text Macros. CA had provided "Object Specific" macros for only those attributes they believe to be useful.

Why isn't there a "Porch Room"?

Scott, It's not really the Annoset. It is the Layer Set being used in that Layout Box. IAE, There's really nothing else available. I do have a "Plan Name" macro that I use within my "Floor Plan Views" that customizes the "View Name". It uses the Floor Number and the Layer Set Name to dynamically create the name. A modification of that macro might work in a Layout Box.

Open the Layout Box Open the Label M> Object Specific .... This will give you the Referenced File Name, Box Scale, Layer Set, Layer, and a few other things. I don't think there's anything for Annotation Set.

You can use Floor Material Regions. They are by default on the "Material Region" layer but can be moved to other layers if needed.

Attached is a macro that can be inserted in the Default Room Label to provide a Room Number. The Room Number is constructed of the floor_number + schedule number (minus the "R") and will be displayed in the Room Label on the 2nd Line. example: LIVING ROOM 102 There must be a Room Finish Schedule. Rooms not included in a Schedule will not have a Room Number. Room_Number.json