Joe_Carrick

Members
  • Posts

    11783
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. And that the Layout and the Plan are both open.
  2. We've been over this before. Chief doesn't recognize any characters above Alt_0255. We need CA to add Unicode support.
  3. Yes it's only in a RT - and I'm assuming you mean X9 (Version 19), But you also need to use a material with some degree of reflectivity.
  4. Dermot, This has been a problem for some time. It has been suggested before that the Annosets should not only specify the Current Layer Set but optionally also the Current Reference Layer Set and the Referenced Floor Level Alternatively, the Layer Sets could be provided with those items. The options for Referenced Floor Level should be: Foundation <Floor Above> <Floor Below> <Previous Floor> This is the current behavior when changing Floors 1st Floor 2nd Floor 3rd Floor nth Floor Attic Currently I have my system set up to work with the <Previous Floor> scenario, but it would be nice to have the <Floor Above> or <Floor Below> optionally locked. IAE, I almost never want it to change, especially in the Layout. CA should really take a look at setting this up so we can rely on the Layout being consistent.
  5. No, the Wall Details Labels are OOB simply showing the "Framing Layer(s)" of the Walls. If there is more than 1 framing layer in a wall there will be 2 Details. It would be nice if CA provided something like my macro OOB but it's easy enough to just modify the Templates and then you have it customized to your standards.
  6. 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
  7. 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
  8. 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.
  9. 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
  10. CJ, Use a Wall Niche and then move the Panel into that location.
  11. 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.
  12. Notice the date that I posted that - October 17, 2014
  13. Sorry, CA has not yet figured out how to give us this functionality.
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. You think he might need to save some of those brain cells?
  20. 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
  21. 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.
  22. 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"
  23. 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.
  24. 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.