Joe_Carrick

1. If everything there is just lines and text - you should b able to marque select and block. 2. Why do you want to block this? 3. If all else fails, create a CAD Detail from view - that you can block for sure.

What are the objects? Walls, Roof Planes, Doors & Windows can not for example be included in a Block. Most other 3D objects can be Blocked to form an Architectural Block. IAE, 3D objects are not CAD so they can't be combined to create a "CAD Block" and they can't be blocked with 2D CAD Objects.

I've been experimenting and I am able to do a "Word Wrapped" note system using Ruby. The problem that I have at this time is that I'm wrapping at the first space after a set number of characters. That works fairly well for a fixed font such as Courier but it doesn't for work as well for proportional fonts. I will need to figure out a width factor for different characters so that the width of the lines is more consistent. OTOH, maybe it's not that bad even with the proportional font.

Yes, but you need to do something like: x="" if type_code == "RS" x = "XO" elsif type_code == "LS" x = "OX" elsif type_code == "TS" x = "OXO" else x = "X" end x

Big Item that I and others are pushing to ge in X8

Ron, I have it on good authority that this will be in X8

Bernie, For your Note system you might want to check https://chieftalk.chiefarchitect.com/index.php?/topic/4186-the-plan-note-key-schedule-from-a-plant-schedule-video/ as it provides a pretty neat way to do it. It's even possible with a Custom Column in the Schedule to use macros for the notes. Or you can put macros directly into the Label of the object - which means you can customize according to Chief's knowledge of an object. Obviously, those capabilities exist for any object that's included in a Schedule.

This is partially available right now using Custom Schedule Columns and the Components List which can use a macro to get the data. The Callout comes from the schedule and the data from the object comes from the macro in that field of the Component List. But the use of this is currently not set up to provide variation within the macro as much as we need.

As a member of the 2015 User Feedback Panel one of my most important things is making ConDocs as accurate and easy to complete as they can be. Automatic annotation based on the model is therefore right at the top of my list.

While it's true that using the Text Macros the way Perry does to save typing the note over and over is effective, it would be much more effective if we could access the actual Roof Finish Layers, Wall Finish Layers, etc directly from the Plan database via Ruby attributes. Here's an example of how this could work: Chief knows the make up of the Layers of a Wall. If that information was available as Ruby attributes for walls, we could write a macro to create a note specifying exactly that information (down to the main layer) and have that displayed as a Wall Label in the Elevation View or in Sections, Wall Details, etc. The Label would be consistent with the model rather than being just something we type. This is really the only way to be sure the Label is what is in the model rather than something else. It would avoid errors and also provide feedback to the user about what his Wall, Roof, etc was made of.

Sherry, I'm currently only able to keep them organized alphabetically. I have a standard series that I have in my Default Plan Template and my Default Layout Template but that is a pretty large list and it tends to more than fill the screen when I go to select a macro. I've made a suggestion on the "Suggestions Forum" https://chieftalk.chiefarchitect.com/index.php?/topic/4581-text-macro-management-organization/#entry39741 for a Browser with Tree Structure (Folders and Sub Folders). I have also sent that to "suggestions@chiedfarchitect.com". It would be a good idea if everyone would send the same suggestion. In order for it to be high on the priority list they need a lot of requests.

Bernie, Try the "Little Book of Ruby" www.sapphiresteel.com/IMG/pdf/LittleBookOfRuby.pdf That's a pretty good reference - and it's free.

One thing that you will notice using Perry's "Text Macros" is that they are specific to the Current Plan. Changing the macro on one Plan doesn't effect other Plans unless you export it and import it into the other Plan. For things that should always be the same from Plan to Plan I put the macros in my Default Template.

After you create the Slab Foundation, Switch to Stem Walls and draw over the Exterior Footings with "Foundation Walls". You might need to check the box for "Slab at top of Stem Wall".

But not with the latest version I posted

Larry, I would not make "Custom Window Symbols" for what you are using them for. I would start with a Standard Window and work with Casings, Sills, Aprons, Lintels (using Custom Molding Profiles) to get the exact Window configuration. Then I would add that window to my Library. Then when you get that window from the Library it brings along all the detail. Chief's "Custom Window Symbols" were really designed to be "Projection Windows" ie: Applied to the exterior. They still have several problems in how they work and I've reported those - maybe we'll get them fixed in X8.

That might work but you would definitely need to make sure the same material was used for both the countertop and the edge molding in order to avoid the black line. even then, I'm not sure that would do it.

Mark, Sorry about the first one. I didn't have my molding cutter properly indexed to the front of the drawer face. Try this one. Lipped Drawer - JPC2.calibz

With Chief Architect, Ruby is currently limited (mostly) to creating textual data which can be displayed in Labels or Text Boxes. Many Chief Objects have available attributes (data about the object) that can be retrieved within a macro and used to do calculations and return the text to be displayed. What's possible depends mainly on what attributes are available. If there's some text you want to create in Plan or Layout from the data contained in Chief (automatically vs manually entering it) it can in most cases be done using macros. So that's your starting point in deciding what you would like a macro to do.

Mark, My Lip Inset profile is pretty typical for that kind of door - to match how Lip-Inset Hinges fit. Generally, the rabbit around the back face of the door is 3/8"x7/16" and the door/drawer overlaps the face of the cabinet 1/4" all the way around.

Note: When I positioned the Drawer Front I made sure the front face was flush with the radius portion of my Molding Cutter. That's the key to eliminating the line.

Dennis, Starting in Plan View 1. I created a closed polyline with the reverse profile of the edge (like a molding cutter that a cabinet shop would use). 2. I converted that to a Polyline Solid 40" tall. 3. I converted that to a Solid. (I blocked it and added to my library of "Cutting Tools" for future use.) Then I displayed an Elevation View 4. I arranged 4 of these to form a "Frame" with an inside dimension of 32" wide x 6" tall 5. I next created a solid box 36" wide x 8" tall x 3/4" thick and positioned it so that it was centered on the above "Frame" 6. Using Solid Subtraction I cut away each edge of the drawer. I need to do a little testing to see if I can save 3D Faces in the Library - kind of like Molding Profiles but to use to extrude as "Molding Cutters".

Larry, There are some books on Ruby you can download but the language IMO is not very well documented and it takes a bit of work and practice to do some of the things I do with it. If you can tell me what you want a macro to do - I'll tell you if it's possible, practical and what I would charge for it.

Mark, Here's one I created using Chief Solids. I created a cutting tool to trim the edges - similar to a router bit. Lipped Drawer - JPC.calibz

Mick, You should be able to get rid of the extra lines by specifying in the Structure Tab of the Foundation Wall Defaults - Hang Floor Platform Above on Wall.