Joe_Carrick

Members
  • Posts

    11923
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. 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
  2. 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.
  3. 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.
  4. All four conditions together. Read the first paragraph.
  5. Yes, add a floor below the 1st floor. IOW, you need a Basement.
  6. Not me. Maybe Michael or Gerry ?
  7. 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.
  8. Larry, Does your Automatic Dimensions Default specify to "Use Layer for Text Style"?
  9. 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.
  10. 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.
  11. Chris, This is true for all dimensions except "Automatic Dimensions". Check it carfully.
  12. Maybe an additional "Annoset" and "Active" Default for "Automatic Dimensions" would be better.
  13. 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.
  14. 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.
  15. Hi Mick, Another possibility is to use .round(3) to get just 3 decimal places max.
  16. 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.
  17. Then: Name the rooms on both floors "DumbWaiter" Insert a door or pass thru on each floor of the size and position desired.
  18. 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.
  19. I'm not sure if it's separate from the overall plan scale - but it might be. I just checked, and there's only one scale for the plan. But each CAD Detail, Section & Elevation can have a different scale. IOW, each "drawing" has it's own scale. All Floor Plan Views are considered a single "drawing".
  20. Check the scale in the Plumbing Saved Plan view. Check what the scale is set when sending to Layout If both of those fail to make a difference - just "Rescale" the Layout Box.
  21. Here in Southern California we have both "Wild Fire Requirements" as well as mountain areas where the temperature can get well below freezing. That means we need to be able to: Prevent embers & excessive temperatures from entering attics and foundation crawl spaces, both of which must be ventilated. Prevent freezing temperatures from getting into these areas which might cause pipes to burst as well as causing cold floors, etc. The Vulcan products work very well for the "Wild Fire Requirements" and are relatively inexpensive. Once activated they have to be replaced but at least they drastically reduce the potential for the structure to be lost. Self closing Vents (temperature activated by thermo-springs) are needed for crawl spaces in the mountains (anything above 3000 ft elevation). These are quite a bit more expensive. Unfortunately, the Vulcan products do not satisfy that so in many cases we need a combination. When I have a project that needs both types of protection I have to detail a dual vent installation with the "Self Closing Vent" a couple of inches inside the "Vulcan Vent". IAE, I really wish there was a combination unit. Maybe I should apply for a patent.
  22. So basically in terms of the ConDocs you simply specify these things and don't worry about the actual vent symbols having any special intelligence built-in.
  23. Depending on the area (Fire Danger, Possible Freeze, etc) foundation and attic vents may need to be auto closing How do you handle those conditions? It would be great if there were Symbols for those specific types of Vents.