Joe_Carrick

Ben, I think you misunderstood the question I was posing. I didn't mean we should prevent this type of questions. What I'm asking is how can we make it easier to get the answers. In most cases I assume the user has tried to get the answer from the help file or from Chief's videos. Often that doesn't get them where they need to be. What can be done to make it easier to get the answers from such other sources?

Probably

Annik, I will do it tonight. I am tied up with a lot of other projects today.

Select the Wall you want to copy - save it to the Library. Now select that wall in the Library and simply draw the garage with that wall definition. This is a great way to build a library of wall types - just be sure to create sub-folder(s) to put your custom wall types in. It's much better than just using the "Default Exterior and Interior Walls".

Sherry, Country is COOL and we welcome your presence. and the opportunity to help.

So basically Rich did what I said in my second option of post #17 of this thread. Not a bad guess. Putting Windows in before creating the first symbol would work but they wouldn't be in the Window Schedule. Doors would essentially be impossible

Hmmmm...... It would be great if some of those "off topic" posts could be deleted (by the OP or a moderator). It would also be nice if the OP could go back and rename the thread and add Tags - but I'm not sure how the Tags are used.

There are so many questions (in some cases - Why can't I......) posted here. Many (and I really think most) of these questions result in an answer of "You Can". There are several reasons for all these questions: 1. It's easier to just ask than to go searching the help files or searching the Forums for previous answers. 2. Most of the time someone will answer the query so the person asking the question is not encouraged to search. 3. This software is very complex - with many different ways of doing something, but not necessarily the same way as other software such as AutoCAD. 4. Few new users take the time to view the training videos, study the help docs, etc. 5. There are several "Hidden Handshakes" that even experienced users may be unaware of - things that get you into an edit mode that you didn't know about. There are probably a lot more reasons, but I believe the 5 above are the main culprits. What do we do about it? What can we? Should we?

No argument from me! The Doorway Category is missing from the materials list. Why it's not treated like a Door I don't know.

If the macro could be inserted in the the Callout as the beginning "Letter" or a part of that. ie D%door.floor% then the numbering of doors would be: D101,D102,... for the Doors on Floor 1 D201,D202,... for the Doors on Floor 2 D301,D302,... for the Doors on Floor 3 etc. This would be true even if there was only a single schedule that encompassed all floors. ps: This is a feature request that I've made previously but in a much more general form (give us Ruby access to all the data of objects - which of course includes floor.)

Dennis, I just used a Box, made a Box to subtract, copied it to each panel location and used the Boolean (Subtraction) to cut the holes. Then I put a big panel 1/2" thick to fill in all the holes and converted it to a symbol. It would be appropriate to set a stretch plane at x=3 and x=-3 so that the vertical rails would remain constant.

Ahhhh...... There is no default "Doorway" line in the Components List for a Doorway. In order for the User Defined Category to be displayed in the schedule you have to add that category to the schedule as a separate column. The other option would be to use an actual Door instead of a Doorway and set the material to "Opening - No Material". You would probably also need to do some visibility editing of the door in Plan.

If the Floor Number of the Door or Window or Cabinet, etc was available as a Ruby Attribute - then we could use that in a macro and it would work for all floors in a single schedule.

Mike, The power of Ruby and Macros is good - but CA really needs to expand it so it's easier to use and has access to all the various objects and their parameters. What would be really great is if Chief had a set of macros doing such formatting tasks that could be inserted into user defined macros (within the define macro tool). Sort of a "Super Macro Subroutine Library". In your case, it could be something like: w = width - 1.625 %format_inches(w,8)% -or- %format_inches(width-1.625,8)% Having this kind of capability with predefined subroutines would make Chief's Ruby/Macro capability much easier for the novice.

Sub Category is not the correct line item. Check the actual Door line in the Components List and edit that Description Field

Hi Tommy, OK, here's one - very simple Shaker Style. I can do a raised panel if you need it. Door - 10 Panel for Tommy.calibz

Tommy, Give me the dimensions and the panel style, etc and I'll knock it out for you. Also, does this need to have a wood grain following the rails, stiles and panel separations or is a solid non-directional material OK?

I would say that he probably used roof planes sloped the opposite direction - but in order to have the normal roof structure there would need to be invisible walls and maybe a second floor where the attic exists. Another option would be to create the walls, convert them to symbols and rotate them to the desired slope - but you would still need the invisible walls and some wall editing.

Check the Components List. I'm pretty sure that's where the Description Field in the Schedule comes from

Greg, What version of Chief are you working in?

Arthur's answer is the best. Open the Symbol in your Library and Generate 2D Block. Then it will be correct when inserted into a Plan.

Mike, Try the following. It subtracts 1-5/8 from the width. The it breaks that into inches and fractions and formats it to the nearest 1/8". If you want the result to the nearest 1/16" just change the (8's) in line 3 to (16's). w = width-1.625 inches = w.floor frac = (w.remainder(inches)*8).round.quo(8) case when frac == 1 result = "#{inches + 1}" when frac == 0 result = "#{inches}" else result = "#{inches} #{frac}" end result

You might have to modify this a bit depending on what you want for rounding. Basically, you need to calculate the result before the formatting. For fractions you would need to use another divmod of one of the array values. w = width-1.625 arr = w.round.divmod(12) "#{arr[0]}#{arr[1].round}" If you can give me an example of a width and what you want the final output to look like I can give you a perfect macro.

arr = width.round.divmod(12) arr = arr-1.625 "#{arr[0]}#{arr[1].round}"

Considering the use, I would do the same. It could be created in Plan but the machinations required to get the orientation and 2D Block right would be quite complicated. I'm really not sure why the Molding Polyline is not available in Elevation. I'm pretty sure that it was in a previous version.