Joe_Carrick

As Michael said, with a Solid or Non-Transparent Background Room Fill.

Make the glass "Opaque"

Maybe it's in the Library, maybe not. -or- It could be in the X9 Final Release but not in the X9 Beta. We just won't know until ..................

I'm always amazed at your ability to remember and use dozens of Hotkeys and Combinations. I'm pretty much limited to the Ctrl-Key standards (Copy/Paste/Paste in Place/Cut/Delete/Undo) Consequently I am a "Mouse" user for almost anything else. I am comfortable using Menus and Toolbars much more than Hotkeys.

I'm ok with it as is. I don't expect to have to use it that much so the extra step isn't a big deal to me. The reason is probably just to keep the Edit Toolbar from becoming crowded.

Larry, I think Hotkeys are the only way to do it. I use "S,D,G" for "Select Drawing Group". You could also assign Hotkeys for "Move Forward" and "Send Back" - but "View Drawing Order" is more difficult.

You can send from any Plan to any Layout. You just can't have more than 1 Layout open in Chief at the same time. I have the main Plan and 5-6 others open and send views from each of the Plans to the same Layout.

Yes, absolutely you can. It's just not automatic. You have to specify each the same.

Picture = 1000 words

At the bottom-right of the user's post click on the green up arrow.

Eventually, the Components dbx will probably disappear entirely. For now, it's still needed for adding Sub-Categories. X9 just put the Code, Comments, Description and Manufacturer in the Object dbx and made those fields persistent. It would be nice to have some additional "user" fields but that's not yet available. IAE, those fields are still in the Components and they have corresponding attributes.

It's now in the Window dbx, Object Information Panel

Check "Show on All Floors"

I use those provided by CA. There are options within the Callout dbx that cover just about everything I need.

Active Camera Callouts are always displayed on the Plan. If you close the Section/Elevation View the Callout will follow the Layer display settings.

Best solution for this is to have your Dimension Text Style set as Not Transparent by unchecking the "Transparent" checkbox in the Text Style dbx.

My mistake. I know some users who were heading to Orlando last Thursday and assumed the show was Friday-Sunday. I guess those guys were just going a few days early.

That's what we've been told. The NAHB/NKBA show in Orlando was over the weekend, and they demoed X9 there so the public Beta should be out post haste.

OK, that makes a lot of sense. I will try to get CA to include those Ruby modules - but obviously it won't be easy.

What would Ruby's CSV module do that couldn't be done with a defined method to read and build a "struct" or "hash" from the csv contents?

FWIW, I don't believe CA charges the manufacturer. AFAIK, they just need permission and the 3D Symbols. In some cases CA might not need the 3D Symbols but I'm not sure about that.

Gerry, I am looking at the possibility of creating a Struct: Struct.new("Cabinets", :brand_series, :door_style, :overlay,....) must have the max number of members defined Struct::Cabinets.new(<string read from a csv>) ie: ["Conestoga Premium", "TW-10", "0.5"] Struct::Cabinets.new(<string read from a csv>) ie: ["Conestoga Economy", "TW-10", "0.5"] I would envision setting this up to fill the contents of the "Comments" by inserting a macro into that OIP field for a Cabinet. The "Manufacturer" field might have "Conestoga Premium" as it's contents - thus triggering the retrieval of the correct :brand_series data. This could expand the data available available to include such things as Door Style, Overlay, Hinge type, etc. All of these could be listed in the Comments column of the Schedule. It would even be possible to have extend this to use the "Description" to subclass within a given :brand/series. All the data would be in a csv exported from an Excel file. Empty columns would simply be ignored. Does this make sense to you? OTOH, it would be much better if CA simply provided access to all the other attributes

You should post this on the HD Forum.

Mark, One thing I noticed above was that you had width<9' and until 9" Ruby doesn't like that. Change it to width<(9*12) and until 9 and it should work - at least that part.

I don't know of any way to do that other than deleting the existing Terrain on Level 1 and then creating it on Level 0. I believe that might cause some other problems.