Joe_Carrick

referenced ? obj = referenced : obj = owner if obj.is_double_door asize = (obj.width/2).round.divmod(12) result = "DBL #{asize[0]}/#{asize[1].round}" else asize = obj.width.round.divmod(12) result = "#{asize[0]}/#{asize[1].round}" end asize = obj.height.round.divmod(12) result = result + ",#{asize[0]}/#{asize[1].round}"

You need a Ruby "User" macro. Here's one for you - name it PolyArea referenced ? obj=referenced : obj=owner obj.area.round(0) - or- owner.area.round(0) That's all there is to it.

I decided to take another look at this. referenced ? obj = referenced : obj = owner if obj.is_double_door asize = (obj.width/2).round.divmod(12) result = "DBL #{asize[0]}/#{asize[1].round}" else asize = obj.width.round.divmod(12) result = "#{asize[0]}/#{asize[1].round}" end Definitely simpler and the 1st line eliminates the need to set the "Context".

When sending views to Layout, it's handy to have the Layout Project Browser displayed. That allows you to see what predefined pages are available - even if there's no data on them currently. By having predefined and named pages in the Layout Page Table of your Layout Template it's much easier to consistently organize your Layouts. You can have extra pages defined that you might not use in all projects, but they will be there when you need them.

One note on centering - using a fixed font is more reliable because all the characters in the string (including spaces will be the same width.

Actually, if you use a User Macro you can format the entire label to be centered. You just need to use the method ".center(20)" for each line. You will also need to use "\n" where you want a line feed. Basically something like this: result = line1.center(20) + "\n" + line2.center(20)

Size1 is an array. Add this to the last line .sub("[","").sub("]","")

I think you forgot to close the file first.

Look in the Bonus Library under CAD Blocks and Details > CAD Details > Foundations

Levis, Try this instead: if is_double_door size1 = (width/2).round.divmod(12) else size1 = width.round.divmod(12) end "#{size1[0]}/#{size1[1].round}" if is_double_door result = "DBL #{size1}" else result = size1 end result.to_s.sub(", ","/")

Levis, Just change when dbl = true to when dbl or when dbl == true

Alan, If you use Text Styles, etc for different scales (designated on a per layer basis) using different Annosets / Layer Sets for different scales, then when you change the scale of a layout box the text will conform to what's set in the Plan for that Layer Set. That's a much better way of controlling the scale and annotation sizes.

Alan, You could use a single Detail Plan with multiple CAD Details (mixed categories) but then you might have some different scales and it would be more difficult to find a specific Detail. I just find it easier to organize by having separate Plans for each category. It's similar to having the Folders in the Library.

If you create Text and set it to "Use Text Style" and then create a Block with other CAD Objects and add that to the Library ..... The Text displayed in the Library will not be "to scale" with the rest of the graphics. OTOH if you set the text to "Use Layer for Text Style" or "Use Custom Text" it will be "to scale" with the rest of the graphics. This is something that I never figured out before and was very frustrated when I found a CAD Block in the Library that had a mess of Text and I couldn't see what the #@&! it was supposed to be.

I have all my: Window Details in individual CAD Detail Windows within a Window Detail Plan Door Details in individual CAD Detail Windows within a Door Detail Plan Railing Details in individual CAD Detail Windows within a Railing Detail Plan etc..... Each CAD Detail Window is named in the Project Browser as a way to identify it.

Please post questions in the Q&A Forum, not the Tips Forum

Dropbox will work but you have to make sure 2 users aren't working on the file at the same time.

The point is that once you send the views to layout that part of the job is done as long as you don't delete the Cameras. The Layout Box is in the Layout and when you make changes to the Plan those Layout Boxes are updated. You just work in the model and your ConDocs are virtually done. You might have a little bit to do but not much.

Then Create a CAD Detail from View and further refine it. ps: I would probably set the drawing Scale of the CAD Detail to 1"=1'-0"

I use a modified version of the SAM. Basically I use a Template. But in my world any Plan/Layout combination is a set of Templates that can be used to start a new project. It's just a matter of deleting the things in the Plan that I don't want for the new project. All Cameras (Section and Elevation) are kept along with the Terrain Boundary, etc. Floor Plans, Framing, Foundation & Roof Planes are deleted to start fresh. I utilize a "Clean Layers" Layer Set to make it easy to clean up the project. Note: All Schedules are in CAD Detail Windows along with my Site Area Analysis Text Block and a few other things so they automatically carry over.

There isn't a set of macros for: Project or any Consultants I use a set of Text Files in the Plan Folder. I use a macro to read those Text Files a display the data as needed. I sell that package for $35.00

I will try to clarify this. When working in a Plan, everything is at REAL WORLD SIZE - no matter what scale is set. All dimensional input and display the actual size that the project will be built. The Layout is a set of pages of paper - and everything there is at PAPER SIZE. Normally when you send a view to layout, the scale you are using in your Plan is the scale that it will be in the Layout - but you can select the Layout Box and re-scale as needed. If you want to work on the actual Plan, just double click on the Layout Box and the view will be opened in the Plan where you can work at REAL WORLD SIZE.

FWIW, I already have a FloatClass.rb with similar but mine does Metric as well.

Cameras are any Perspective or Section/Elevation View that have been saved. Wall Details are the Wall Framing Elevations (created automatically when you "Build Wall Framing"

Technically you are correct. But for the amateurs it's sometimes simpler to show a sequence of commands rather than the most elegant programming syntax. Also, you didn't show the definition of to_ftin that would be needed to put the slash in. I've found that most Chief users (at least on the forum) are very reluctant to learn Ruby.