Joe_Carrick

Members
  • Posts

    11783
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. 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.
  2. 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.
  3. You can use Floor Material Regions. They are by default on the "Material Region" layer but can be moved to other layers if needed.
  4. 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
  5. Ahhhh.... The difference between Windows and Mac ?
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. X1 is quite old so I can't say for sure - but you may have turned off "Connect CAD Segments" in Preferences>CAD.
  11. Since the text is actually a part of the 2D Block, the answer is "No".
  12. If you have several CAD Detail Plans, it's pretty easy to organize by Detail Subject. Door & Window Details Railing Details Foundation Details Floor Framing Details Roof Framing Details etc Each of those Plan Files can have multiple named CAD Detail Windows. It's kind of a "Library of Details" that are available to be sent to any Layout. They can be modified in those Plans and any Layout that references one of those details would be automatically updated. It's also very easy to create new details from any of those. The Details are always "to scale" and the Library doesn't get cluttered with hundreds of details that can be difficult to locate.
  13. Considering those restrictions, I would suggest a reversal of the Plan with the Living Room at the back and the Kitchen adjacent to the Garage so that you don't have to carry groceries, etc so far. Eliminate the door into the Garage from the "Entry" side of the house - it's really not needed and is a security problem. Based on your stated lot size and assumed setbacks you may have difficulty with driving into the Garage. You may need to relocate the Garage Door if the street is on the left or reduce the depth . It all depends on the site orientation and setbacks. Without that information it's difficult to give any better advice.
  14. Richard, I agree with regard to Project Specific Details and Notes. But many notes and details are "standard" and need not be in the Project Folder. "Code References" should of course be Project Specific and I would have those in a CAD Detail in the Plan. I will have to check on the "duplicate names" that you mention as always being first found in the same Folder as the Layout. IMO it shouldn't work that way but I would never have such a condition anyway.
  15. Richard, It works like this: When sending to Layout Chief first looks for an open Layout If none found it looks for a Layout the same name as the Plan in the Plan Folder If that's not found then it will use the Default Layout File Layout Boxes all have a link to the Plan & View that they came from (it's a full qualified path, filename and view) If that location, file & view doesn't exist then you would need to relink
  16. If they are in the Chief Data Folder (or a subfolder thereof) you might need to relink. If they are in a folder independent of the Chief Architect version then no relink would be needed. That's probably the best solution - something like "My Documents/Chief Architect Notes and Details". In my case, I use a Folder in Dropbox and I retain the old Chief Architect versions and all their folders. Currently I have X4, X5, X6, X7, X8 and X9 all available. It's probably time to clean out some of those - at least as archives.
  17. Just keep the Main Plan File and the Layout File in the same directory. All other Plan Files (General Notes, Details, etc) can be in another folder. I prefer to keep them subfolder(s) in the Chief Data Folder.
  18. I sent you a PM with my phone number and email address.
  19. A lot of that can be done in Chief using Solid Color Fills with about 50% transparency. In some cases the Terrain Features can be used because they are already Polyline Objects that can have a fill. In other cases you would have to create the closed Polylines.
  20. Then it's no longer an active view and any changes in the Plan will not be reflected in the Layout.
  21. I'm not an expert on Scissor Trusses - but I'm pretty sure that "No Birdsmouth" should cause the Ceiling to be higher than the Top of the Plate - and "With Birdsmouth" should make it match the Top of Plate. The critical thing is to get all that set up (figured out and coordinated) before creating the Ceiling Planes & Trusses. I think Chief's recommendation of creating the Ceiling Plane at the outside of the wall is only appropriate for "No Birdsmouth". Otherwise the Ceiling Planes should be at the inside of the wall. IMO "No Birdsmouth" is the better way to build Trusses and there should be added plate support (ripped to match bottom chord slope).
  22. Notes in the Plan is the way to go. General Notes in Text Boxes in the Layout is OK, but you can also have those in Plan CAD Details sent to Layout. Leader Lines in Layout is not a good idea.