Joe_Carrick

File>Import They will automatically be installed in the Library.

Sorry, I don't - but all Chief's "Object Specific" that contain a "." and not a "_" are unavailable for calculations. In most cases this is just the "Room Data". You will note that my macro shows the corresponding macros that do work. example: internal.area .... doesn't work internal_area .... works I'm pretty sure that the "Object Specific" for "Rooms" are the main ones that don't work. I think CA has converted almost everything else except their "Global" macros.

Hi Mo, I've attached my macro that lists all of the attributes of an object. It is sorted alphabetically and skips the attributes that are simply indication of if it's using the defaults for that object. If you import this into your plans you can select any object, open TMM and select this macro. It will show you all the available information and the names of the attributes that can be used in custom macros - or even directly in labels. If you need any help in using such attributes, let me know. _Object Properties wo _is_default.json

Michael, I'm not sure, but I think she's interested in knowing what the macros are that correspond to those and can be used in calculations. If so, then the only way I know of getting such a list if by use of an "_Object_Properties" macro. I have 3 of those depending on the amount of information needed. (full, short, short wo defaults). Rather complex macro to write but well worth it if doing any serious macro development.

No, I was referring to the offset within a 6" stud wall.

Actually, just offset 1". That will work perfectly.

Like this?

When you select the exterior room there's an icon on the edit toolbar (usually at the bottom of the screen) to create a "Living Area Polyline". Once created it pretty easy to modify it to the overall perimeter of the building.

Dermot, This is no longer true. Cabinet Doors, Drawers, Panels, etc are now included in the cabinet attributes. Your argument about "Bloat" doesn't make sense. You suggest that we could put the sinks, appliances, accessories, etc in as freestanding objects instead of inserting them. If "Bloat" is really the issue then doing what you suggest would cause it. IAE, the number of sinks in a plan is never as much as the number of windows & doors. BTW, The Fixture Schedule can pick up the data from these items so why can't they be included in the attributes of the cabinets.

Most likely you will need to use "Saved Plan Views" sent to Layout. Each "Saved Plan View" can have a different Layerset. This will allow you to control what's displayed in each Layout view.

You could use a special wall type with a main layer that is thinner and "Recess to Main Layer".

Depends on getting rid of the state dictator

During this Covid pandemic we can't arrainge meetings with anyone at the building departments here in San Diego County. They've essentially been unavailable.

I'm curious as to why you are having this problem. The "Create Stairwell" tool should handle this without you needing to add any invisible or divider walls. Can you post the plan file so we can really help?

In the Polyline dbx check the boxes: Show Length Show Angle They will then be displayed and automatically updated as you edit them. Note that this can only be done for each individual Line, Arc, or Polyline in its dbx. There is no default to make that setting - it's stricly on an individual object basis. The format of the display is specified in the CAD Defaults.

Gene, Have you tried using multi-panel bifold doors. For me they work fine to represent the "Fold and Stack" either inside or outside.

Rob, You don't really need the "Doorway". You can specify the casings, etc for the "Mulled Unit"

It's obvious that there are a lot of different configurations available today from various manufacturers. For CA to program all possible cases would be IMO unreasonable. For those cases that are not available as automatic options in Chief we can use combinations of doors an mull them to create what we need. Yes, it's more work for us but once we've done it ..... It can be saved in the Library for future use. IMO that's the kind of thing I get paid for and I just don't think it's reasonable to expect CA to program every special condition.

There's a way to do it with just one Schedule and some tricky placement(s) in the Layout. I'll let you ponder that concept.

Make a 2 panel next to a single fixed and mull them. Like this

Bruce, Why are you using a CAD Detail for your Elevations? It seems you are causing more problems by doing that. Just send the Elevations to Layout and then manipulate the layerset there if needed..

In the Options Panel of the dbx set the left to 3 and the right to 0 - or - right to 3 and left to 0 Chief will show 2 of the panels as sliding. Note that Chief will by default show the "Inside Panels" as sliding - but you can reverse the "swing" to make it the outside panels.

I was going to explain but Michael put it quite simply.

Saved Plan Views should exist for each floor. If you change floors while in a Saved Plan View you have changed that view. In fact any changes you make to a "Saved Plan View" will be shown in the Layout where that view has been sent. So create a new "Saved Plan View" for each floor and each building discipline. Then make sure you have the correct "Saved Plan View" active when you send to Layout.

I just use the Ruby website Index of Files, Classes & Methods in Ruby 2.6.5 (Ru by 2.6.5) (ruby-doc.org) It has all the details for Ruby programming. The one thing that Chief's Ruby implementation does provide is "PUTS" but otherwise ......