Joe_Carrick

Rene, $Global variables can be assigned values from an object - but they are not attached to the object. OTOH, you can assign any value (including a $Global) to any field in an object's OIP. Just be aware that if the $Global"s value is change then that OIP field will also change. I have some macros that rely on the current view Layerset name. Unfortunately that is assigned to the object when it's created so it's not going to be available for the object. My solution is to place an invisible text in each view with a macro to assign the Layerset name to a $Global. That $Global will always be the name of the current view Layerset as long as the Layerset of the view isn't changed. I had requested years ago that Chief add a $Global for the current Layerset but they simply added the NVP for each objects layerset. To store a value in an object use an OIP field. To assign a value to a $Global use an objects NVP or any other value you want. BTW, a $Global can be an array if you want to store a lot of different values. $p[n] where n is specific to the object. A Hash could also be used, depending on how you want to be able to identify the values for retrieval.

For an asymetric door you will need 2 versions. This is not a matter of "Change Hinge Side" - rather it's a matter of the actual swing.

I think I understand. It's kind of the same as the previous problems (prior to current X15 version) with symbols stored in the Library. What object did you include in the style palette? I assume there wasn't any way to replace that object with a current X15 version object.

no idea - post the plan

Larry, Is this a Client Logo & Title Block? If so, for different Clients - just relink the PDF on page 0 (default template page) Also note you can have different templates specified for different pages in the Layout so the PDF could be different for those pages.

I don't think there's any way to do that automatically. I'm assuming you would have different PDFs on different pages at different locations on the pages. A mask on a default page would always be at a specific location, not relative to the PDFs.

Larry, I'm assuming you want to have some text over-writing an area of the PDF. If that's the case, just use a text block with a white fill. That's how I do it.

Search in "3D Warehouse" for Models "Clothes Line". There are a lot of them. btw, I haven't seen those used here in California, USA for about 50 years. We had them when I was still living in my parent's house before I went to college. Now almost everyone has an electric or gas clothes dryer.

This would be IMO a very difficult programming task. Chief's walls are very special objects which define the vertical limits of rooms. If a sloped window wall is what's wanted I would simply create a symbol using a post to ceiling glass panel railing, defined as a geometric shape. I would set a z stretch plane at + 12". Then I would place it in the plan and rotate about the y axis to the angle desired. I would make the wall where I place this as a single layer transparent wall. Perhaps if Chief were to create a "Window Wall" tool with the ability to specify a slope it could work - but it would need to also define the room as other than contained simply in a vertical wall.

if you use Wall Types set as "Partition Walls" they won't cut the finish flooring, intersecting walls or ceilings. I'm using X15 so I'm not sure if that's the same in X10 - but it should be.

Where was the macro assigned in the Style Pallet? If it was in the Components you can: Open the Library Object Select Open Object Components and make your change there. I don't know of any other way to get a macro into a Style Pallet.

My wife is coming with me and we have booked a suite at the Hampton Suites next to LePeeps. We have other friends that live about 30 miles north which we will also be visiting.

So in X15 you can select the object in the library and edit its macros by right clicking on the library object and selecting "Text Macro Management". My methodology is to copy/paste the X15 macro content into the existing macro and rename it as needed.

I'm not referring to your template plans. There shouldn't be any problems with plans created using X15 templates that are using X15 macros. The problems would only occur when a Library Object created in X14 (or before) with embedded macros is added to an X15 plan. Those macros wouldn't be the same as the ones in the plan and so might be incompatible.

It was almost all related to NVPs in macros for openings (doors & windows). Also since I rewrote almost all of my user macros for X15 and renamed some of them to X15 conventions (no spaces in macro names) there were a lot of macros that were no longer valid in those plans. If you don't use many macros in your plans you shouldn't have too much problem. That's not my way of working. For example, I have macros for openings (doors and windows), walls and roof planes which provide different labels in plan views than in elevations & sections. Almost everything in my plans and layouts are annotated my these very comprehensive macros.

I've attached a set of macros that can be used in "Text Macro Management" to display the available Global Variables and the available NVPs for any selected object. These can be very handy to determine what information is available to be included in labels, schedules or user macros. Enjoy Global & Object Porperties.json

There are similar "layers" NVPs for Walls, Floors, Ceilings & Material Regions. Check the "Object Properties Macros" I posted Global & Object Properties Macros - Tips & Techniques - ChiefTalk Forum (chiefarchitect.com)

For the Plan View, %owner.layers[0].material_data.description% placed in the Roof Plane Label should do it. -or- %owner.layers[0].material_data.description% -over- %owner.layers[1].material_data.description% if you also want to indicate the underlayment. To get it in the Schedule you will need a custom field - but the same macro should work.

Some notes about moving to X15. Some X14 macros won't work in X15 due to NVP changes. If you have a project that was started in X14 or before - be careful not to open and save it in X15 Make sure you only use X15 compatible macros in new plans User Library Objects from prior to X15 may have imbedded macros that won't work in X15 Those should be modified to be X15 compatible. IOW, check the differences and make sure you account for them. I had one project that was almost completed and I inadvertently opened it in X15, made some changes and saved it, overwriting the X14 version. It took quite a lot of time to make the corrections so everything worked properly.

You have to select the drawer itself in the front/sides/back face panel.

My problem with using Schedules for this is that I can't specify an area to be in more than one Schedule. Basically I have many closed Polylines all on floor level 1 I want all of them to be in Schedule A some of them in Schedule B some in Schedule C etc. I need to display totals for each Schedule as well as some calculated totals (added, and/or subtracted) Schedules currently just don't have the flexibility I need.

What happen if you edit one of the existing walls?

Not mine, not by a long shot. There are a lot of mistakes in this macro. Some NVPs in X15 have different names than in X14, including the fact that the Base Cabinets type is now "Base cabinet". it would be better to just assign: nomen = obj.type[0].upcase which would pick up B, W, F depending on the cabinet Also, the line hinging = owner.door_swing should be hinging = obj.door_swing In my macros I use comprehensive error handling by use of: begin some code... rescue exception code... end so that my macros will never result in "evaluation error"

Regardless if it's been reported by someone else or not, go ahead and report it. Squeaky Wheel.............

These symbols have some serious problems in terms of how they open and what's required in terms of casings/trim. You really need to look at some actual manufactured bookcase doors to see what they really need to be. Also, the 2D Plan View CAD is totally wrong unless you specify about an 8" thickness but it should also be consistent with the wall thickness or visa-versa. The problem with that is Chief limits the door thickness to 4" I would be inclined to make my own symbols for these - but probably start with those in that catalog or "a wall cabinets w/o doors" and modify as needed. The advantage with using a cabinet is that you can have "face frames".