Joe_Carrick

Since this system only works in X8 (and is a bit more than just one macro) I've decided not to include it as a part of the Macro a Month Club. Some of the Club subscribers are still using X7 so I need to limit the monthly macros to those that will work in X7. However, I will be offering it as a stand-alone package with all the functionality shown in the video plus a few more calculation macros for just $25. For the Macro a Month Club the package will be priced at $15 as an addition. I need a few more days to put it all together with instructions. You can email me joe.carrick@dslextreme.com if interested.

The thicker wall occurs when there's a floor or ceiling height difference between the rooms. The it changes to the wall thickness above or below. Do a section cut thru that division wall and you'll understand.

This video shows how Area analysis can be easily done in X8 using Polyline Labels. Each Polyline simply needs to be on a distinctly named layer, and one of my macros being inserted in the Label. That takes care of collecting the areas and storing them in a Global Memory Hash Table. Secondary macros take care of displaying a variety of calculated results. The possibilities are basically unlimited as to what calculations can be performed. The video shows the use of 5 additional macros to calculate and display the various areas. Once this is set up, any modifications made to the Polylines is instantly updated to the displayed Labels and calculated results. http://screencast.com/t/HtOWWXv1

Scott, Why would anyone want to build that at all?

No need for a correction. X7 Libraries are compatible with X8. You just need to "Open with X8" when you download.

If CA is listening, this would be a great place for superscript annotation where feet are normal characters and inches are superscript characters. IOW, a 36" x 54" SH window would be label 3046SH as the automatic label but the 0 & 6 would be superscript characters. I've seen several cases where the size was misinterpreted. OTOH, I use a Window Schedule with Callouts for my Labels. It's much easier to specify the sizes that way.

In your default window label you can use %width%%height%%type_code% which will give you the width & height in inches instead.

Check this

I would create some CAD Lines (construction lines) at the those locations and just snap the Pool Walls to the intersection of those construction lines.

I don't believe so. What's wrong with just using the dimensions as shown?

Sorry Jon, I misunderstood the problem. You're saying that you get this message when you open the Library? I thought such a message was only on a per plan basis. You should contact CA SSA and report this problem directly. I haven't seen it on any of my systems but it's probably due to a Texture/Material Folder location. It could be fairly easy to resolve just by correcting the path.

Jon, Have you tried displaying a 3D Framing Overview to see which items are creating the problem? It could be that simple.

The X8 Framing Schedule has some problems in how it lists the Nominal Size and Materials. Note that the Nominal Size for Lumber members are listed with the " sign. This is contrary to drafting conventions. ie: 2" X 6" indicates a true size - standard practice would be to use a lower case "x" and actually use 2x6 which indicates the nominal size. Header Material should be FIR FRAMING. The designation of FIR STUD 16" OC is totally silly. Also note that there are a couple of posts listed as COLOR - BRICK instead of STEEL. Due to the complexity of properly listing the actual material we either need to leave that column out of our Framing Schedules or very carefully create and use better names for the materials. Unfortunately Chief automatically assigns some of those materials and the place where they can be edited is not very convenient. Headers for example can only be edited in Wall Details. For the Type Column a ROUND Post could be a Pipe Column or it could be Concrete. Again, due to the complexities Chief either needs to expand the possible Types or add a Description Field that can be used for Framing Members.

Done!

This is a very bad bug. I use the Wall Type name for Labels on Exterior Elevations.

I sent you an email.

Think differently (innovate) A. Top Cabinet is Wall Cabinet B. Shelving on sides are Open Front Cabinets rotated 90 degrees C. Add Freestanding Doors I show it exploded in the pic. btw, This is basically the way it would be built if ordered from any of the cabinet manufacturers. It's just 2 tall cabinets with shelves(no doors), one 24" deep wall cabinet with doors, and a couple of separate doors. Depending on the hinging you might need some additional jamb strips for the tall doors. That's a detail for the cabinet supplier to deal with.

Scott, You have issues. Gerry and I do not. We have some differences of opinion but basically agree. CA has very little desire to provide additional access to Ruby enhancements. I think Gerry and I both believe that with just a little bit more work on CA's part that there would be very little we couldn't do. But there are only a few of us that make suggestions about Ruby and that means CA doesn't rank those requests as very important. The fact that they have their own "Global Macros" with data that can be displayed but that the underlying values (text or numeric) are not available to use in User Macros is to me just another indication that they aren't interested in providing anything extra. They would definitely not want to spend the time to provide any sort of complex area analysis - so I think you can forget that idea.

Gerry, After about 10-15 minutes into the video you showed a Property Area, an Undeveloped Area, a Developed Area and a Building Area. They didn't match up as you were explaining what you had. At that point I quit watching because: 1. I didn't believe your "spread sheet" 2. There was no explanation of the calculations. Please go back and look at those numbers shown in the video and explain. Thanks, Joe ps: I don't think anyone wants to watch a video that starts with 5 minutes of your desktop and just listening to a mono-log without seeing anything actually being done. Then you opened X8 and spent considerable amount of time showing a Plan and some Tables (including primarily the one in question). I - and I believe most Chief Users - don't have the time to listen to you talk without a cogent demonstration of how you do the thing you are talking about. We just don't want to watch over an hour or two for what could be shown in a single 10-15 minute video

I tried to watch Gerry's videos. Unfortunately they are too long and verbose - I just don't have the time to devote to watching for that long. Consequently I don't know what he has or hasn't done. One thing that I did notice was that the first Area Analysis that he showed seemed to have many discrepancies in the displayed values. IAE, the basic principle for using the Polyline Labels is to have a macro (only one is needed if done correctly) that can be assigned to the Label of the Polyline Objects that need to have their areas stored in a Global Variable. Then, as Gerry stated a series of macros can be created to perform the appropriate calculations (add,subtract, multiply, divide) and display the results. Some of those would be: FAR (Floor Area Ratio) Site Coverage Total Building Area (all floors) Total Building Area (per floor - in case there are multiple buildings) Total Impermiable Area etc. By having each Polyline Area "named" (there are a couple of ways to do this) you can simply display the areas with their names, and use the same techniques in the calculation macros. For those who belong to my Macro a Month Club I will provide a set of macros and a SHORT video of how to use this to do any analysis you might need. I will have that done by next Monday, 1/18/2015. I will post the video in this Forum (General Q & A) My apologies Gerry for the Hi-Jack but it seems other users had already done so.

It would be possible if there was Unicode support in Chief's Ruby implementation. Currently, Chief only supports ASCII characters in Ruby Strings. The superscript characters for 0-9 are u2079-u2079 using the Arial Font. The ASCII characters are u0021-u007E. Basically these are all the Characters you can type on the keyboard. Anything above u007F is unavailable.

Considering that this is done with OpenGL using the GPU I woudn't have expecting anything else.

See post #3 in this thread. It needs to be a part of the Door Tool as a Door Type - not a set of static Symbols that have no decent functionality. As I said before, this Library is worthless. It should never have been done as a set of symbols.

IMO the worst possible solution.

These symbols IMNSHO are just about worthless. It would have been far better if Chief had spent the time to allow "bi-fold" doors to have a specified number of panels - or just added a "Folding Window Wall" (aka NanaWall) door type. That way we could have full flexibility to show them Open or Closed as well as being able to directly insert them into a wall with all the other Door features.