Joe_Carrick

Members
 View Profile  See their activity

  • Posts

    11881

  • Joined

  • Last visited

 Content Type 

Everything posted by Joe_Carrick

  1. Joe_Carrick
    Notice the date that I posted that - October 17, 2014
  2. Joe_Carrick
    Sorry, CA has not yet figured out how to give us this functionality.
  3. Joe_Carrick
    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.
  4. Joe_Carrick
    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.
  5. Joe_Carrick
    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.
  6. Joe_Carrick
    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.
  7. Joe_Carrick
    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.
  8. Joe_Carrick
    You think he might need to save some of those brain cells?
  9. Joe_Carrick
    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
  10. Joe_Carrick
    Ed, You need to make this request in Suggestions
  11. Joe_Carrick
    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.
  12. Joe_Carrick
    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"
  13. Joe_Carrick
    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.
  14. Joe_Carrick
    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.
  15. Joe_Carrick
    Why isn't there a "Porch Room"?
  16. Joe_Carrick
    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.
  17. Joe_Carrick
    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.
  18. Joe_Carrick
    You can use Floor Material Regions. They are by default on the "Material Region" layer but can be moved to other layers if needed.
  19. Joe_Carrick
    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
  20. Joe_Carrick
    Ahhhh.... The difference between Windows and Mac ?
  21. Joe_Carrick
    You need to upgrade to X9
  22. Joe_Carrick
    I think that's what you get paid for when the client requests a change at this stage of the project. Edit Area might help for some of it but it might take a bit more than that.
  23. Joe_Carrick
    The best way to handle this is to use the Defaults for each Wall class (Exterior, Interior, Foundation, Railing, etc)l. You can use the %wall_type% macro or a custom user macro. I use a custom macro that uses the floor_number, wall_id & wall_type. Example: Wall 1.29 [Siding-4] This also has the benefit of placing those names in the Wall Details section of the Project Browser.
  24. Joe_Carrick
    If there are no macros in the text..... is the arrow really referencing a specific object? If so, which object? There may be overlapping objects and the arrow could be attaching to the wrong one. This brings up another little (maybe not so little) problem: The arrows don't always connect to the correct object. When there are overlapping objects, a macro designed to reference a specific object type, the arrow might connect to the wrong object. An example of this could be a roof plane. If the arrow is connected in the overhang area it works fine, but if it happens to hit on a wall or even a room it won't connect to the roof plane. It would be really nice if the system was smart enough to connect only to an object for which the macro(s) were valid.
  25. Joe_Carrick
    This is interesting. I had never noticed that the line with an arrow would be deleted if the object it was "connected to" was deleted. I normally use "smart" annotation and only want the leader line to disappear when I delete the text. OTOH, if I do in fact delete the object I think I might also like the leader & annotation to be deleted - but maybe not always. In my testing, I found that when a "leader line" is used: if the object is deleted the leader line is deleted but the text box will remain if the text box is deleted the leader line will also be deleted if the arrow is moved to another object the original object can be deleted without effecting the leader line if the arrow is just moved to an empty arrow, deleting the original object also deletes the leader line It's an interesting set of "rules" that probably shouldn't apply to "dumb" annotation (ie: no macros). IOW, when there are no macros in the annotation the arrows and text should be independent of any other objects.