Joe_Carrick

So in each system just set the additional LOAD+PATH as a separate line in the Ruby dbx. It's that simple.

That bug should have been fixed by a later update. Check for updates in your digital locker.

Yep, every time there's an update or new version. That's why it's not a good idea.

For rb files that you wish to use in multiple versions of Chief you will need to make sure you copy them to the current version's $LOAD_PATH. -or- put them in a common file and edit the $LOAD_PATH in the current version of Chief. I'm pretty sure you can have multiple paths separated by simi-colons

Agreed- except that AFAIK, Chief's default Safe Level has always been 2 I do have some macros that create, read and write files. Some of those require a Safe Level of "0".

You probably need to set the Ruby Safe Level to 1. CA by default sets it at 2 which doesn't allow some things to work.

I think there's a bit more that needs to be done to make it work correctly: Macro: In CA require 'scope1' my_method(length) Output: from text stored on a local drive def my_method(x) rafter_length = (self.to_f.round / 12) + 1 convert_to_int = rafter_length.even? case when convert_to_int == true result = rafter_length when convert_to_int == false result = rafter_length +1 end end Unless I'm wrong, the parmeter length needs to be passed to my_method in order for the method to know what's being analyzed.

I just find it easier to have Saved Plan Views with the appropriate defaults and layer sets. That's what I send to Layout. In addition, for Details, Elevations, Sections, etc I find it easier if my drawing sheets sizes for those items are sized to fit uniformly within my layout border. It's much easier to arrange them by snapping to one another. I am aware of your method but I don't like having to go thru each sheet in the Layout to make sure the Defaults, Layerset and any Reference Layersets are properly specified. Saved Plan Views sent to Layout take care of all that. Actually I don't think your method deals with "multiple reference layer sets" on separate Layout pages.

Here's a sample rb file that has a series of defined methods. Note that I no longer use this since it's problematical to update with each new version of chief. #================================================= # Joe's Macro Subscription Service # Ruby script: Float Class # Copyright October 1, 2015 by Joseph P. Carrick #================================================= # The contents of this Ruby Macro is not to be # revealed to any other Chief Architect user or # employee. If a violation of this requirement # is found, the offending subscriber's # subscription will be immediately terminated. #================================================= # Place this file in Chief Architect/Data/Scripts # folder. Then place the following: # require "Float Class.rb" # at the beginning of any macro where you want to # use these methods #================================================= class Float #================================================================= # Display a numerical value formatted according the the current # units of the Plan. Requires $Units to be either "Imperial" or # "Metric" to recognize the units. #================================================================= def format_number(n) if $Units.nil? result = self.sig(3) elsif $Units == "Imperial" result = self.ftin(32) elsif $Units == "Metric" result = self.meters(n) else nvalue = self.sig(3) end return result end #================================================================= # Display a value (decimal inches) formatted as a text string # syntax: nvalue.ftin(denominator) # example: n = 64.125 # s = n.ftin(8) -> 5'-4 1/8" #================================================================= def ftin(denominator) if $Units.nil? nvalue = self elsif $Units == "Imperial" nvalue = self elsif $Units == "Metric" nvalue = self/2.54 else nvalue = self end arr = self.divmod(12) if arr[1] >= 11.96875 arr[0] = arr[0]+1 arr[1] = 0.00 end inch_frac = ((arr[1]-arr[1].floor)*denominator).round.quo(denominator) if arr[0].floor < 1 if inch_frac == 1.0 result = "#{arr[1].ceil}"+'"' elsif inch_frac == 0.0 result = "#{arr[1].floor}"+'"' elsif inch_frac < 1 and arr[1].floor > 0 result = "#{arr[1].floor} #{inch_frac}"+'"' elsif inch_frac < 1 result = "#{inch_frac}"+'"' else result = "#{arr[1].floor} #{inch_frac}"+'"' end else if inch_frac == 1.0 result = "#{arr[0]}'-#{arr[1].ceil}"+'"' elsif inch_frac == 0.0 result = "#{arr[0]}'-#{arr[1].floor}"+'"' else result = "#{arr[0].floor}'-#{arr[1].floor} #{inch_frac}"+'"' end end return result end #======================================= # Convert Float to Feet # rounded to nearest foot #======================================= def feet feet = (self/12).round(0).to_s result = feet +"'-0" return result+'"' end #======================================= # Convert Float to Decimal Feet # rounded to 3 decimal places #======================================= def decimal_feet feet = (self/12).round(3).to_s + "'" return feet end #======================================= # Convert Float to Inches-Fractions # Formats are: # 1/16" # 1 1/16" # 1" # nDivisor can be any integer between # 1 and 32. Most common are: # 1,2,4,8,16 & 32 #======================================= def inches(nDivisor) inches = self.floor if inches > 0.00 frac = (self.remainder(inches)*nDivisor).round.quo(nDivisor) else frac = (self * nDivisor).round.quo(nDivisor) end if frac == 1 result = "#{inches + 1}" elsif frac == 0 result = "#{inches}" else result = "#{inches} #{frac}" end return result.gsub(" ","-")+'"' end #================================================================= # Get the SqRt of a number to n significant places #================================================================= def sqrt(n) a = self x = 1.00000 while (x*x) < a x = x+0.00001 end return x.round(n) end #================================================================= # Display a decimal value as a text string to (n) significant places # syntax: nvalue.sig(n) # example: x = 65.375 # s = x.sig(4) -> '65.3750' # example: x = 65.25 # s = x.sig(3) -> '65.250' #================================================================= def sig(n) nPad = self.round().to_s.length + n + 1 result = self.round(n).to_s.ljust(nPad,"0") return result end #================================================================= # Convert millimeters to meters & display to (n) significant places # syntax: nvalue.meters(n) # example: x = 6543 # s = x.meters(3) -> '65.430 m' # example: x = 650 # s = x.meters(3) -> '6.500 m' #================================================================= def meters(n) if $Units.nil? nvalue = self elsif $Units == "Imperial" nvalue = self*2.54 elsif $Units == "Metric" nvalue = self else nvalue = self end if n > 3 n = 3 elsif n < 0 n = 0 end m = nvalue/100 result = m.sig(n).to_s + " m" return result end end

You don't read the rb file. You "require" it. Within that file you need to define the function"int_length"and then in your macro you call the function. ie: result = int_length(length)

You should just make this an evaluated macro in chief, context: owner rafter_length = (length.to_f.round / 12) + 1 convert_to_int = rafter_length.even? case when convert_to_int == true result = rafter_length when convert_to_int == false result = rafter_length +1 end Using an rb in this case is superfluous. IAE, to use one you would need to "require" it in your chief macro and then call any specific "defined" function within that rb file. The only reason for using an rb file is for utility functions that aren't otherwise available that you would need in many different user macros. This one is object specific to any object that has a "length" attribute.

Here's a pic of how I do it. The Logs are 9" diameter "Swedish Cope" and the Chinked Wall Type is 6" thick. I put the door and window in first and then stacked the Log Symbols (8" vertical) using the transform/replicate tool. BTW, I usea a similar system for Tilt-up Concrete.

I don't know what your ACAD Blocks include - I assume they are mostly Details. If that's the case I would definitely be interested if you can export the Library.

That's what you get with stock cabinets. I use a company that is much more flexible in their sizes. OTOH, I never have to specify the door or drawer sizes. The Cabinet Manufacturer does it automatically even when I specify odd sizes down to 1/16" increments.

Try adjusting the toekick height and/or countertop height or thickness. You need to have the cabinet itself (not including the toekick) exactly 1/2" more than the sum of the drawers.

Chief doesn't seem to have a way of placing window screens on windows. I know that renderings probably look better without screens but they really should be present even if repressed for rendering. How do you handle the specification of window screens ? Should Chief provide a way to specify them other than just a "comment" ?

I just noticed that I can specify different Drawing Sheet sizes for each view in a Plan. Is this a new capability with X14? I don't recall being able to do that previously. It's really nice for positioning of Details, etc in Layout. Maybe what I'm thinking of is just that we couldn't have different page sizes within a Layout.

If you are using the "Place Library Object" for your Toolbar Buttons then you can assign any ICON you want.

I like all my Floor Plan Views ( Architectural, Foundation, Framing, Elecrical, Mechanical, Plumbing, etc ) at exactly the same location in the Layout. In order to make this easy: I display the drawing sheet in all such views - but not in Elevation and Section Views. I specify margins matching the Layout ( left, top, right, bottom ) I position the drawing sheet so that my model fits within the margins. Then when I send a plan view to layout I specify "Entire Plan/View" The above ensures that all my Plan Views are at the same exact position on each page of the Layout. It also allows me to see that the Plan will fit on the current drawing sheet size. If it doesn't I just change the drawing sheet and Layout Page sizes (my Layout Templates)

It's kind of simple. to get the WMR for the entire wall you just click anyplace on the wall.

The above is just for a Custom Home and I didn't include the interior non-bearing stud walls. If it was a remodel I might need 3 times as many Wall Types to deal with Existing, Demo & New. Arrrgh !!!

So, by way of explanation, I'm doing a project with SIPs. I have 2 thicknesses of the SIPs (4" & 6") and the following wall surfaces: 5/8" Drywall both sides 5/8" Drywall Interior 1" Stucco Exterior 5/8" Drywall one side - other side exposed framing 1" Stucco both sides Stone Veneer Exterior 5/8" Drywall Interior Stone Veneer Exterior - other side exposed framing So that can add up to a total of 12 Wall Types - just for this project alone. OTOH, it's only 2 basic Structural Walls & 3 sets of Finish Layers which could be WMR's. Based on the possibility of Stud Wall, CMUs, Concrete, etc plus a couple of other finishes it's easily possible to wind up with another 40-50 distinct Wall Assemblies. In order to avoid having to define several wall types for each new project I save them in my Library. This is why I would consider changing my methodology - but only if I could still have the full wall definition in the Wall Schedule.

Try adjusting the color of the material to a lighter shade of grey and make sure it's set to "Blend with Texture"

For the round circle (foundation detail & top of wall) use a "Round Arrowhead" and size it as needed.

It would simplify the Wall Types by having only about 8-10 Wall Types (Just the Structural Layers) All Finish Layers would be WMR's. Currently I have about 100 Wall Types in my Library - various structural mixed with all sorts of finishes. IOW, I wouldn't need different Wall Types for every possible set of Finish Layers - Interior & Exterior.