Joe_Carrick

What version of Chief are you using?

One place where I use this extensively is with a custom Rich Text Block for my Room Labels. Everything in that RTB is a macro accessing the Room attributes. Some of those macros are Chief supplied and some of them are my own custom macros. When I put that RTB in a Room it picks up all the information and displays it. I can even place it outside a room with an arrow to pick up the data.

If you want a true 3D standing seam roof, you will need to model it using 3D molding PLines or some other actual 3D objects. Textures in Chief are not really 3D. They are only representations (pics taken from one direction) and depending on the z dimension (if it's more than about 1/2") of the material they won't be very realistic

Text and Rich Text can't currently be saved to the Library without first creating a CAD Block. That causes some problems when the text contains an evaluated macro. Basically, the block has to be "unblocked" after placement before it can recognize the context in order for the macro to work correctly. The solution to this is to have a CAD Detail in your Template/Plan that has the Text and Rich Text annotations. I use this as a sort of "Warehouse" for commonly used notes, titles, etc. I can simply select one of the items in this CAD Detail, copy and then place anyplace you need to have that annotation.

I have been very busy updating my entire set of macros for X11. Most of them still worked but some of the new capabilities of X11 pushed me to redo a lot of them. I will be done with this effort in another week and will post an update to the Macro list and be ready to sell them. ps: We've also been preparing our house for sale and the clean-up / de-clutter has consumed a tremendous amount of my time.

Schedule order?

Mick, If you make it a "Note" instead and save that to the Library you can skip the Block. Just put the macro in the "Text above the Line" field of the Note

In reality, 3080 indicates a 3'0"x8'0" door. It's standard annotation. If you order a 3080 door from any manufacturer that's what you'll get.

Annosets / Active Defaults / Dimension Defaults allow control of the Arrow Style and Size. But that's only for New Dimensions. To get the same kind of control (for common dimension strings) that the Layer Set provides for Text Style we would need another column in the LDO. "Arrow Style" might be sufficient.

All four conditions together. Read the first paragraph.

Yes, add a floor below the 1st floor. IOW, you need a Basement.

Not me. Maybe Michael or Gerry ?

Note that this still doesn't solve the issue of Arrow Size, Arrow Style, or Layer according to "Active Defaults" for Auto Dims. I've reported it as a bug and will let you know what answer I get from CA.

Larry, Does your Automatic Dimensions Default specify to "Use Layer for Text Style"?

Larry, I believe Chris may be using a Layer Set that has a different Text Style for the "Dimensions, Automatic" layer. That would account for the text size. OTOH, I am relatively sure it won't account for the layer being anything different.

Chris, The issue is only the "Layer" specified in the "Dimension Defaults". Auto Dims are always created on the "Dimensions, Automatic" Layer instead of the Layer in the Active Defaults.

Chris, This is true for all dimensions except "Automatic Dimensions". Check it carfully.

Maybe an additional "Annoset" and "Active" Default for "Automatic Dimensions" would be better.

If you have an Annoset in use that specifies a specific Layer in the Dimensions Default: All dimensions should then be created using that Layer But that's not the case. IMO this is a BUG that needs to be fixed. I will report it.

But they are Annoset & Layer Set specific.

Larry, As Chris indicated it's all tied into the "Saved Plan View". Basically when you open a "Saved Plan View": An Annoset is selected which has "Dimension Defaults" and the Dimension Text may be even be set to use the Text Style of the Dimension Layer. In your case it appears you have "Active Defaults" selected rather than a "Floor Plan Annoset" Using "Active Defaults" is a problem because it can so easily be changed. It's best to save your "Plan Views" with named Annosets and make sure the correct Annoset is selected.

Hi Mick, Another possibility is to use .round(3) to get just 3 decimal places max.

Note, if you want to actually perform calculations using those values - you need to have a custom evaluated macro. example: Macro Named "MyCustomMacro" or whatever and your object's visible_length = 498 inches obj = owner x = obj.visible_length/12 x = x.to_s + " ft." The result would be 41.5 ft. That last line make x a string instead of a floating point number. The key here is that Chief's built-in macros display a value but you can't use it for anything else. By creating a macro that accesses the underlying attribute you the capability to manipulate the data and use it for more complex labeling.

Then: Name the rooms on both floors "DumbWaiter" Insert a door or pass thru on each floor of the size and position desired.

I use the following: Foundation .... Level 0 Basement & Other Floors … Levels 1 - n Attic Living Space... Level n+1 Attic ... Level A Note that in my scheme the "First Floor" could be on either Level 1 or 2, depending on if there's a Basement. Floor Numbers are not always the same as Floor Levels.