Joe_Carrick

Are you sure? Post the Plan........

They are worth watching. The biggest problem is finding exactly what is available for what object....... For example: A Layout Box contains an anttribute (amongst others) referenced_full_filename which is the full path and filename of the file that was sent to the Layout. This can be used to construct additional filenames to read and write. Interestingly, the context for using this is "Owner" because you would have to put the macro in the Label of the Layout Box. Chief has not documented all the attributes available and where and how to use them. That's one of the biggest shortcomings. It would be really nice to have a complete list (indexed and searchable) but at this point the Ruby Console is the only source of that information. The other problem - and it's one I believe will be alleviated in the next release or two - is that a lot of object data is still not available to Ruby. One of those is something Justin asked about - Ridge Height.

Kelly, Try the NKBA Auto Interior. They are much better.

Any good lawyer (oxymoron) would pierce that scam in about a NY minute.

Kelly, Why not use Auto Dimensions? If there are some you don't want you can just grab the extension line and move it - that dimension will disappear. But you are correct that the Manual Dimension Tools are picking up more than just the Main Layer. I don't recall that in X6 - but OTOH, I seldom use Manual Dimensions.

Larry, Don't even think about doing any Condo projects if you don't have insurance. I won't do them anyway just because there is always going to be a lawsuit and you'll lose everything you own if you don't have a lot of coverage. The same thing is true for most commercial buildings. The insurance is one reason that Architects have to charge more. We have to carry coverage on our projects well into the future and it's the client who is going to have to pay for it.

Yep, Labels are "Owned" by their object. the Rafter is the "Owner" and that's the object that has the length. You could use a context of None but then you would need to specify owner.length instead of just length.

Wherever a dialog is when you close it will normally be where it is when you open it the next time. There might be something in Preferences that would change that but I don't think so.

Justin, I'm totally in agreement with you on the use of macros. There is so much power available by using them - it just takes some time to get it set up. You could further simplify your macro to: (length/24).ceil*2 You don't need anything more than that.

Does anyone have a "Fixed Font" similar to Arial? I really don't like Courier New (looks like typewriter output) but I don't know of any other font that I can use to insure nice neat columns of text and numbers.

Your CAD Blocks were created at "Real World Size" so if you want them to appear at a scale of 1/2"=1'-0" you would need to reduce the size to 1/24. An easier way to deal with this is to place your details in CAD Detail Windows in a Plan File and then just send to Layout at 1/2"=1'-0" Scale. I never use the Library for Details.

Even that's not really correct since the finish_floor_elevation is likely not 0.00 even on the 1st floor. If you really want the finished ceiling height you need to used both attributes. There really is no reason to take a short cut - the macro if written correctly will work for all floors.

Thanks Alan. I don't do much remodel work but using multiple Plan Files is also my preferred method.

For those of you who do a lot of remodel work. Have you considered using 2 or even 3 Plan Files to show: 1. Existing and Demolition 2. New or 1. Existing 2. Demolition 3. New IOW, having 2-3 Plan Files with one Layout File? It would seem this could really simplify the ConDocs by avoiding having to show New and Demo at the same time. It would also make it easier to determine the existing areas vs the finished areas.

Thanks Joey and Alan. That will help me put together a demo that will cover your type of work. BTW Alan, the "Building Coverage %" in your example doesn't appear to be correct. That's one thing that I want to prevent.

I'm trying to put together as comprehensive a set of Building and Site Data as I can. What do you show on your Permit Submittals? Site Area ? Buildable Area ? Livable Area per Floor ? Total Livable Area ? Site Coverage ? 1st Floor Area 1st Floor % of Site Area? Floor Area Ration (Total Livable Area vs Site Area)? Paved Area ? ....anything else ? Pics of the Plan Data section of your ConDocs would be a real help.

There are additional settings for RO and Trimmers.

Make sure you review the Ruby tutorial and experiment with it to see what is available. It would also be a good idea to go back to the 1st post in this thread and read carefully what it says about "Context". Labels are "Owned" by their object - so in the case of a macro used in a Label (room. door, cabinet, window, wall, etc) the context must be "Owner". Labels are the only thing that I know of at this time that uses the "Owner" context. Text Blocks that connect to Polylines or other CAD objects via an arrow require a "Referenced" context. Macros that do not rely on any Chief Object to retrieve data - such as general notes, etc. do not need to be any context other than "None". The Text in these macros can be typed and/or the values contained in "Ruby Global Variables".

No! No! No! That is an absolute elevation measured from 0.00 (aka Level 1 floor). So using that attribute will only work on the 1st floor. On any other floor it will not give you the ceiling height. Chief has the information and it can be used to advantage only if you use it correctly. You must use (finish_ceiling elevation - finish_floor_elevation) to get the finish ceiling height.

Ray, 1. The context must be set as "Owner". 2. You must add the macro in the "Default Room Label". That's the only place it will work. 3. Probably not what you wanted to hear.

What do you mean by wall artifacts? We can't read your mind.

That would be the best way to do it. You could copy all the columns, etc to the second floor by Copy/Paste Hold Position or just adjust the ceiling height in the warehouse area so that the second floor in that area becomes a zero ceiling ht.

Place the Library Microwave in your Plan as a Free Standing Object (not in a cabinet). Now resize it as needed and add it to your User Library. It will now be the size you need to place in a cabinet.

My method is a little different than Gerry's (I allow the specification of the fractional denominator and I format the output differently when the value is less than a foot) but essentially the answer to your question is yes - but only by adding a macro to the Default Room Label. Using Gerry's basic code the macro would need to be: arr = (ceiling_elevation-floor_elevation).divmod(12) inch_frac = ((arr[1]-arr[1].floor)*16).round.quo(16) result = case inch_frac when Rational(1.0) "#{arr[0]}'-#{arr[1].ceil}\"" when Rational(0.0) "#{arr[0]}'-#{arr[1].floor}\"" else "#{arr[0].floor}'-#{arr[1].floor} #{inch_frac}\"" end result + "CLG" I modified Gerry's code mainly by using (ceiling_elevation-floor_elevation) so that it would give the right value. The basic problem with this is that it will just be added to the Room Label on the same line and at the same text size as the Room Name.

Thanks Gerry, My mistake adding the last line. I should have left that off. begin result = owner.area rescue result = referenced.area end "Area = " + result.round(0).to_s + " Sq.Ft." would be correct as would your syntax of: "Area = #{result.round(0)} Sq. Ft." It's easier for me to read the way I show it but both give the same output. IAE, the point of this was to indicate how to have a macro work with either context. Something you pointed out in another thread.