Joe_Carrick

This is one I did about 6 years ago

Hi Jason, In most cases my "rescue" performs an alternate set of code to provide the appropriate value. Sometimes it's just a matter of looking for a different NVP because the suspected object didn't have the NVP I was expecting. In other cases I present a message explaining what's wrong. IOW, an intelligent error correction hint. The last option is just a reasonable value - such as (0 or 1) when the error is "division by zero"

I've also been told that schedule columns are evaluated "Left to Right" so if a macro in column 2 relies on one in column 5 there could be a problem. In that case it would be necessary to either switch the positions or incorporate the value of column 5 directly into the macro in column 2. IAE, Chief will need to do some evaluation of how to make the Schedule get the values from the Row Object; Maybe the macro context could have "Schedule Row Object"

I suspect that's just a screen issue for the type of render being used. If you print to a pdf all the labels should b displayed properly.

Since i prevent all my macros from returning "Error" the incorrect result is something I provide as a default. I do this by using the: begin result = Code that could produce an error rescue result = default value end to trap errors

I kind of blundered into this situation. Basically what it amounts to is that when OIP fields have values assigned by macros (owner context) the macros will report a value for that object. However, if the custom field is used as a column in a Schedule - the macro uses the schedule as the owner and reports an incorrectly calculated value. This is quite simply because schedules don't have any OIP fields the macros can't return any valid data. I've reported this bug to Chief Tech Support. Hopefully they will be able to come up with a solution. but I'm sure it will require some modification of the schedules to make custom field columns to evaluate the data based on using the row object as the owner and that the value can be the result of any macro in that field

Shane, The defaults will only be presented for new room labels. IOW, existing plans will show what it was, not what you change the defaut to. For existing rooms you will need to select all of them and specify the label items you want. Unfortunately things like %room.height.ceiling% and "TEST TEST TEST" will all be at the same size as the %room.name%. So RTB's are still better.

So you should check the room structure elevations. It might be the floor & ceiling structure and finish settings. I don't know if Chief made any changes in the calculations (rounding, etc.) Maybe they just fixed something that was being calculated incorrectly.

If it's one of my macros, I can fix it OTOH, this can be a result of the elevations in the room's structure panel.

Shane, Take a good look at the room defaults. There's a lot of capability there for customization. Personally I'm suppressing the automatic label in plan views and using my RTB labels which I've stored in my user library for plan views. I'm only using the X18 automatic label in cross sections.

Have you sent this in as a bug?

You might also note that since the Layout and the Plan are separate - Macros in them are also separate. So you can have a macro in each with the same name but totally different script and result. My Layout files have only 25 macros and only 6 or 7 are duplicated in the Plan file. OTOH, my Plan files have over 175 macros.

Unfortunately for me, going to the UGM in Idaho is just to much money. My RTB room labels use Arial Normal but with Bold, Underline & sometimes Italic. Here are a few examples: All of this information is presented by custom macros. I don't currently use a check for "room type" but I do check some NVPs. Are you really able to do this with the current room labels.

Hi Tyler, For my room labels I'm still using "Rich Text" that I've stored in the Library. This allows me to have different text styles & sizes on each line of the label. I have several different RTB's that cover the area, dimensions, ceiling height, etc depending on the room types. I currently have to manually place these in each room. It doesn't take too much time but having it automatic would definitely be an improvement. It would be great if there was an option in the defaults for each room to use a "named library object". IOW, in the "Room Label" defaults and in the "Room Specification Label" have this: Label Content Automatic Label Specify Label Label Source (library object) This would also need to be in the "Room Types" defaults so each room type could be different. Mainly I'm interested simply to get the automatic placement in the room(s), but I might also want to vary other parameters such as layer or color. I would think this could be fairly simple to program - just the source of the label to be used.

Why not put them in the User Library? Another option would be Text Macros.