Joe_Carrick

Block it then add to Library. If the text contains a macro then you just edit the macro.

So now I've found that your macro does in fact get all the roof planes as separate in the $tree hash. I'm not sure exactly how that's working but it's good. The bigger problem is that the $tree hash grows drastically with each edit of the plan. It needs to be refreshed from nil whenever an edit is done.

Brown Tiger, How do you get $tree to contain a different hash key for each roof plane? My experience shows that the object_id in Chief is not reliably different for different roof planes. IOW, I am pretty sure the data for each successive roof plane will overwrite the previous. I would love to be proven wrong.

Joey, Do you want the "X" or "x" ? Is rounding to the nearest inch also acceptable? This is a pretty easy one for me and it can be placed in the default door and window labels.

Here's another way to deal with this sort of problem. Add these lines to your macro: #================================================ # Refresh if more than 2 seconds has elapsed #================================================ if $MyGlobalRefreshTime.nil? $MyGlobalRefreshTime = Time.now end if Time.now > $MyGlobalRefreshTime + 2 $MyGlobal = nil $MyGlobalRefreshTime = Time.now end Then whenever you hit the F5 key twice the macro will execute, setting the $Global to nil which will cause the macro you have to set it to do its job. I use this little trick to update hashes when I make changes.

Rene, I'm going to assume that your macro is using a $Global variable. If you have not closed Chief then the value is a holdover from the previous plan. One solution is to clear the $Global open the Ruby Console - you can leave it open since it's a non-modal dialog type the $Global variable name and set it to nil ---- $MyGlobal = nil <enter> press the F5 key twice to force the macros to execute. The macro in your current plan will update the $Global variable

Yes, those should be there. I notice that your macro is now working. But of course the only thing that's being displayed is the "automatic_label". $tree is a Hash that contains the other information. That's not displayed because it's not the last thing in the macro.

I'm still seeing those "?" in the last 2 lines of your macro.

What are the "?" doing in the last two lines of your macro ? They shouldn't be there

I use a Polyline ( P/L LineStyle ) for my lot boundary --> Property Area I use a Polyline ( S/B LineStyle ) for my setbacks --> Buildable Area Other Polylines ( Named Layers ) define various object types. I also use the demolition, existing and new (my own creation) to identify how building areas are to be treated. I have a single macro in the Polyline Labels that accumulate the areas into a Hash which is then accessed by several other macros to display the data in tables with totals.

No, it just hides the Terrain and of course the Terrain Feature at that location. Basically it graphically removes them where the Symbol or Building exists. From a logical standpoint It seems to me that the area should be reduced by the size of the object.

I place a s Symbol (or a Building) in an area where there's a Terrain Feature (Sidewalk, Driveway or Stepping Stone) it cuts a hole in the Terrain. However, the reported area of the Terrain Feature doesn't reflect the change caused by the hole. Shouldn't that are be reported as reduced?

I also like Rene's method. I made a few tweaks for my own purposes: Created a 8" concrete stem wall with a thin white plaster interior surface - added to Library Created moldings for both the cove base and the tile coping - added to Library Use a thin tiled cove molding for the water-line (1/4" thick x 6" high) Use a Room Ceiling for the water surface This eliminates the need for any additional molding polylines and just moving the walls results in everything being adjusted accordingly.

I am available and I live in San Marcos. Please PM me with your contact information.

Glenn's right. It requires some Ruby macros. I have a set of macro's that get and display the areas of each roof planes. It wouldn't be very difficult for me to modify and display the data as you want. I would probably store the output in a CAD Detail but it could be sent to Layout on any page you want.

It's probably better to ask "Can this be done?" But essentially it's only limited by what data CA has and will in the future expose as object attributes that Ruby can use. It can't be used to actually edit the model but for annotation purposes almost anything is possible.

Thanks for the video. I think I will set up your method so I can use it in the future. Just need to get all the pieces together and organize in my user library. Some questions: What did you use for the Pool Deck (slab, stepping stone, etc) so that it automatically adjusted when you changed the size/shape of the pool? Couldn't you use the "ceiling" as the water surface instead of a molding?

You need to click on the Stair and then select the "Auto Stairwell" icon on the "Edit Toolbar". That will create the opening in the floor above.

When (which version) did CA add the ability to name our user defined "line styles" and retrieve the name from the Ruby attributes? I remember years ago that the user defined "line styles" were only given a number and there wasn't any way to get the actual name. I know I had mentioned it to someone at CA (Jason I think) but I had no clue that the real names were now available. Whoever did it and whenever they did it -- Mucho Gracias.

Thanks for the offer - but I'm more interested in a generic approach that I can use for a variety of different shapes and configurations. Ideally, it would be a specific tool (Terrain Feature - Swimming Pool) with all the options. I'm probably just dreaming. For now, I will plan on using Robert's method - at least until something better comes to mind.

Maybe X12 since it's nearing Beta testing. I think the CA staff is probably already using X12 - at least some of them would be.

When was the video made? Maybe it's a feature that will only be in a future release...…

Hi Robert, That's a pretty nice solution. I'm not sure how well it would work with a oval or kidney shaped pool. One of the things I am most interested in is being able to get and display the areas of water and the pool deck as separate items. The PSolid and Roof Plane should be sufficient for that.

I've been trying to come up with a way of doing this so that: It looks right in 3D There's an optional Pool Deck Edge (probably a Molding) The Slab (Pool Deck) has a hole that moves with the Pool Pool Surface is below top of the Slab Pool has a variable depth It's not easy. Does anyone have a great method for doing it?

You have to specify the room as the thing you want to get the internal_area of. Try this macro: ######################################################## # Macro Name: "room_internal_area" # Displays the internal area of the room a Note is in. ######################################################## # Copywrite by Joseph P. Carrick, August 2, 2019 ######################################################## referenced ? obj= referenced : obj=owner begin obj.room.internal_area.round(2) rescue "object isn't a Room" end You have to specify the room as the thing you want to get the internal_area of.