Joe_Carrick

There shouldn't be a problem as long as both files are open at the same time. You will have to display the plan (view with the macro that assigns the value to the global variable) first. Then display the Layout page that retrieves the value. I do this sometimes but I agree with Chopsaw - it's easier if it's done in a text box within the plan file itself.

Probably because of the code block syntax you used. In Ruby it's common practice to use the method .to_f to convert a string to a floating point value or the method .to_i to convert to an integer value. You can also use the method .to_s to convert a numerical value to a string. I'm not personally a great fan of code blocks - mostly because I don't fully understand all the nuances of their use. I also think not using code blocks makes the script easier to read and understand.

Consider using your macros in the Labels of Rooms, CAD Boxes, etc. That way you can use the dimensional data (Ruby attributes) of those objects to calculate and display results. If those results are stored as global variables you can have a macro in a text box that retrieves the data and displays it as needed.

Bill, I don't understand your last post. Your Global Variables are all string values. To perform math you need to convert to floating point If you are just looking up values from a table it should work. However, it appears that you are actually assigning new values to the Globals. What are you expecting?

Global variables are persistent and can be accessed in other macros. $TO $CFL $ep can all be used in other macros within the same session of Chief. In your case: $TO -> "94 #Total occupants LSF"

The problem is that Chief's walls are specifically designed for Doors (and Windows) that need to be vertical. There are no provisions for anything else. Chief simply doesn't cater to walls that are not vertical. As Gene said, you could use Solids but that won't work to define a room - only "Walls" provide that functionality in Chief.

NO

I like to work with my Plan Drawing Sheet matching my Layout Pages. To do this: I create both Templates with the same size & display the "Drawing Sheet" I determine the workable area within the Layout (inside border & title) I set the margins of my Plan Template to match those Layout limits I create a polyline matching the outside of the Plan Drawing Sheet - on a custom Layer "Sheet Boundary" & then I lock that Layer. Now, when workin on a Plan with the "Drawing Sheet" displayed I can see exactly where the plan will be when sent to Layout. The resulting Layout Box will be exactly the same size as the Layout Page, facilitating lining-up all floors in Layout. For CAD Details I typically use a "CAD-Detail" Drawing Sheet size of 5.6825" x 5.6825" as this fits nicely within my Layout Border (4 details high and 5 details wide) on my Arch-D Layout.

Robert, Have you tried hitting the "Done" button? I'm not sure how you started the Ruby Console in Help mode (tutorial) but you can basically clear that gray area by hitting the enter key several times. The only entry area in the console is as Dermot indicated - the bottom "white" area. The gray area is basically a response to what you enter.

and I never use metric - so how did I know that was the problem ???

Anna, Glenn's confusion is probably because you have your drawing units set to "centimeters" instead of "millimeters". For metric plans it's standard practice to use "millimeters".

I would do this by creating a 3 panel bifold (show closed) and a hinged door. They would all be "Glass Panel" with the appropriate frame sizes. Then I would remove all casings, sill, frames, etc. Then I would mull them and make appropriate entries in the OIP, including the Description.

You might also want to modify the "Transparency" of the water.

Nice Larry, I see you have my face at the bottom of your screen.

I made my own with some wood and attached a flat wall mount. Eventually I quit using it because it took up too much desk space and I got reflection from ceiling lights.

I'm pretty sure that was in 2011. The IRC is still 36" but the CRC is 42"-45"

I think there's an exception for such case where sunlight isn't available.

FWIW, the recent Windows Updates - past 4-6 weeks - have caused problems with some printer drivers & possibly other things. I've had to uninstall those updates in order to avoid program crashes when attempting to print from any application to certain network printers. I was told that it would be fixed in the next update but that was 4 updates ago and it isn't fixed yet. I would guess that M's problem is a setting in the NVidea Control Panel that isn't quite right - maybe a resolution setting ???

File>Import They will automatically be installed in the Library.

Sorry, I don't - but all Chief's "Object Specific" that contain a "." and not a "_" are unavailable for calculations. In most cases this is just the "Room Data". You will note that my macro shows the corresponding macros that do work. example: internal.area .... doesn't work internal_area .... works I'm pretty sure that the "Object Specific" for "Rooms" are the main ones that don't work. I think CA has converted almost everything else except their "Global" macros.

Hi Mo, I've attached my macro that lists all of the attributes of an object. It is sorted alphabetically and skips the attributes that are simply indication of if it's using the defaults for that object. If you import this into your plans you can select any object, open TMM and select this macro. It will show you all the available information and the names of the attributes that can be used in custom macros - or even directly in labels. If you need any help in using such attributes, let me know. _Object Properties wo _is_default.json

Michael, I'm not sure, but I think she's interested in knowing what the macros are that correspond to those and can be used in calculations. If so, then the only way I know of getting such a list if by use of an "_Object_Properties" macro. I have 3 of those depending on the amount of information needed. (full, short, short wo defaults). Rather complex macro to write but well worth it if doing any serious macro development.

No, I was referring to the offset within a 6" stud wall.

Actually, just offset 1". That will work perfectly.

Like this?