Joe_Carrick

That will work. The question is ...... What's the price?

Simonas, Most of us use a Door Schedule which includes the Door Size, the Frame Thickness and the RO Size. This provides the required information to all the trades & suppliers. Personally, I use the Callout for the Label so they all have to refer to the Schedule to get the information they need.

I use Callouts for my Door and Window Labels. I have them offset -18" with a solid fill. The problem is that the Dimension Extensions are (at least in X7) not behind the Callouts. That means I have to manually edit the Extensions so that they don't go thru the Callouts. I have not been able to find any way to automatically limit the Extensions or to have the Callouts be the "Front Group". Does anyone know of a way to avoid this problem? I sometimes find that my Roof Planes are also showing on top of the Callouts.

Alan, You are 100% correct for wood frame construction. However, for masonry and concrete construction it is quite common to dimension the rough opening. It then becomes the Door & Window suppliers that have to verify the sizes that will fit. Hopefully the Schedule will show the correct sizes and the RO's are correct in the first place as well as as-built.

Simonas, Put the attached macro in your Door Labels. Ideally, it should be in the Door Default Label so that new doors will automatically have that Label. BTW, the macro is set to round both the width and height to 2 decimal places. If you don't want any decimal places - just edit the macro so that the round(2) is round(0). Door_RO.zip

It can be done with a custom macro.

My suggestion to satisfy the "Printed Scale" problem is to use a Graphic Scale in the Plan. Then no matter what size the Layout is printed at the scale will always be correct.

It's pretty standard in most Apps. Whatever function/tool you are using - F1 should pop up the help. Chief is very good about that and it's a real great way to get a refresher on how to do something. In fact, with Chief if you select an object and hit F1 - it will bring up a list of possible training videos related to editing objects. You can scroll down thru the help file or click on a training video. Using Chief's built in help and tutorials is very handy.

I don't see anything that shows differences in the Cabinet. Can you post the Symbol so i can check it? I'm talking about changing the "Front". It has long been the case that a Cabinet imported from any other app comes in as a base cabinet with a counter top and no ability to change the front configuration. IOW, you can't add doors or drawers. You can't edit the width of the Face Frame. Essentially the only things you can change are materials and the size and/or existence of the Counter Top.

Jon, Can you now edit the Face Elements like a normal Chief Cabinet? I don't think so.

Amazing what's in the Help File. So many times we forget to check that first.

Scott, Select the Object Eyedropper and the press F1. Read the Help File. It will tell you what you want to know.

Scott, I think you will find that will change all the existing cabinets that have that set as (D) - ie Default.

Defaults ? - the Wrench Icon on the Edit Toolbar Object Painter ? - the Eyedropper Icon with "O" on Top Toolbar Match Properties ? - the Match Properties Icon on the Edit Toolbar These all do different but similar things. You need to explain a little more what you want to do. The "Object Painter" was added in X7.

I can't tell for sure why, but one thing is that they are using 2 different fonts.

Scott, By doing it once (positioning that is) and blocking it it can be added to the library - retaining the definition as a cabinet and a geometric shape. Resizing can be done by selecting and tabbing to the individual components. The biggest advantage to this solution is that it only adds 5 faces to the Plan. Using a Cabinet for the Liner adds a minimum of 24 faces but that could go even higher. Another problem with using a Cabinet as Michael outlined is that you would also need to make it Frameless so that the inside cabinet won't show if there's no Door(s) on the outside cabinet. There is also the depth issue because you wouldn't want the "liner" to cover the Face Frame at top and bottom. It's really just the box that would be "lined".

I found an interesting thing about this. I can block the Cabinet and the Liner together and add it to the Library. When I place it in the Plan I have both already placed together as a block. To resize you have to select & tab but that's pretty simple.

Here is a "Cabinet Liner Symbol". It can be sized and positioned as needed. Generally, it should be: width: Cabinet Width - 1 5/8" height: Cabinet Width - 3 1/4" depth: Cabinet Depth - 1 5/8" Position should be 1" from back of cabinet, centered side to side and top to bottom. Cabinet Liner.calibz

Here's another pic - I just manipulated the PSolid a little to cover the interior sides. The next one uses a open front box symbol positioned inside the cabinet. I just created a 3D Box, exploded it and deleted the front face. Then I converted that to a Symbol. It can be adjusted to any needed size.

If is the key word. In the long run, separate materials for: Face Frame Interior Sides Back Interior Top & Bottom would provide the ultimate flexibility.

Since it is very common to have a different color/material for the Face Frame of Cabinets than the interior - it would be appropriate for there to be a separate material selection for the Face Frame. There was another thread where the "Back Material" was also suggested so that it could be "Transparent". This would be a good thing to put in "Suggestions"

So here's a pic of my solution. The Cabinet, Door, Molding and Shelf materials are all set in the Cabinet dbx. I added a thin PSolid inside the Cabinet (Red) to hide the back interior face of the cabinet. You have to make sure it's far enough away from the wall so the cabinet back isn't in front of the PSolid. If you look closely at the inside right corner of the cabinet you will see that the PSolid doesn't quite cover all of the cabinet back - I was a little sloppy Sorry Scott - no Plan but the pic speaks for itself in this case.

I agree with Scott. Dennis' example is misleading because he used a full overlay door and didn't show a view of the sides or top of the cabinet. If the door wasn't a full overlay you would see the cabinet face as the same material as the interior.

Instead of than turning them off.... Make the text size 1" and it's color white. Also, lock the Layer. That way, it's there if you ever need it (maybe to add a macro) but it doesn't get in the way.

OK, so here's the bottom line: Ruby is a pretty basic programming language. It can perform math operations on numerical data and it can manipulate text data. In addition, it can store and retrieve data in Hash Tables and Arrays as well as read and write to computer files. Programming is just understanding the "syntax" and how conditions are handled. The Ruby Syntax is a little different than some other programming languages but IMO is not much more difficult than "Basic" and much easier than a lot of other languages. Ruby uses what are referred to generally as "methods" but I like to think of as modifiers. Here are some examples of how a text string can be modified by Ruby: x = "My Text String" y = x.length --> 14 x = x.upcase --> "MY TEXT STRING" x = x.downcase --> "my text string" x = x.gsub("my ","") --> "text string" x = x + " is now all lower case" --> "text string is now all lower case" if x.length > 14 y = x.length --> 33 else x = "Something Else" end x.rjust(y) -------> " Something Else" Now is everyone totally confused? It's just a matter of making modifications to data.