Joe_Carrick

You could create a Symbol (Exterior Fixture) that mounts on a wall.

Make each of those rows of tile a separate "Wall Material Region" -or- a "Molding Polyline" -or- a "Wall Covering". Either one will work.

In that case - just use a "Soffit" for the dropped ceiling area. No need for a separate room.

Steve, How thick is your invisible wall. Typically a "Room Divider" should be very thin and prevents this problem.

I'm just curious as to why you would use a PSolid instead of either a "Custom Backsplash" or a "Wall Material Region". Both tools are easier and are designed to do the job. You can use the "Pattern From Texture" tool in either case.

Why not just use a custom backsplash or wall material region in that area? You could then use a different material. IAE, you can copy the existing material and change both the texture and the pattern to suit what you want.

The bevels would be difficult. However, you can use a small "Wall Material Region" (transparent material) with "Cuts Surface Layers" to get a fair approximation. Another option is to use one or more Molding Polylines with several moldings stacked to add the Blocks outside of the wall finish layer.

Out here in LALA Land we virtually can't build a CMU wall without lots of steel and solid grout. I have seen some "Garden Walls" that had little or no reinforcing but those usually get flattened the first time an earthquake occurs.

X7 is at least 4, maybe 5 years old. I'm pretty sure the cable railings weren't available for stairs that far back. The key is that the "Panels" section didn't exist.

Yep! And then they mess it up.

If you want a Water Mark - why not just use that tool?

framing_area should be to the outside of the rafters and rough fascia surface_area should be to the outside of the finish fascia and possibly shadow-boards

I like this one much better: #================================================= # Joe's Macro Service # Ruby script: _global Variable Values # Copyright September 22,2019 #================================================= #================================================= # This macro lists all the $Global variables and their current values #================================================= referenced ? obj = referenced : obj = owner if obj.respond_to? "object_type" and obj.object_type.to_s.upcase.include? "TEXT" result = "" else arr = Kernel.global_variables.sort i = 0 j = arr.length - 1 result = "" while i < j x = arr.id2name y = eval(x) result = result + x + "\t = " + y.to_s + "\n" i = i+1 end end result

Marque select the text box. Then you should be able to block it.

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.