wjmdes

Members
  • Posts

    337
  • Joined

  • Last visited

Posts posted by wjmdes

  1. On 7/18/2021 at 9:16 PM, Dermot said:

    As far as I can tell, the built in macros work just fine.  Probably best to talk with Joe about this.

     

    Ugghhh.   I put up this post and did NOT add the image to show what it is doing.

     

    1429284368_clghts.thumb.JPG.48af8af7d10d93197a1c1a41463cc0eb.JPG

     

    The "room label" I created works when placed in the room.  When it is not in the room, it uses the ceiling height value from the room I have it located in.  I will ask Joe...

     

     

  2. I use a simple macro for commercial as-builts to describe room info for clients  (the ceiling height macro is from Joe):

     

    %room.name%

    %room.dimensions%

    %room.ceiling.finish.name% @ %ceiling_Height_Label%±

    %room.floor.finish.name% FLOORING

    Since I started using X13, if the label does not fit, I use a leader line, it appears to gather the ceiling height info from the room the block is in rather than where it is pointing to.  I have been doing it this way for years.  The ceiling height is supposed to be 9', but it is getting its data from the room the block is in.

     

    Hoping someone has a solution...

  3. On 5/3/2021 at 5:44 PM, Joe_Carrick said:

    I'm not personally a great fan of code blocks

    Can you please clarify what you mean by this?  Just trying to learn.

     

     

    9 minutes ago, Alaskan_Son said:

    I didn't study all your methodology or syntax in great deal, but just doing a quick once over, I see that you appear to have a typo in the last line of your code_data macro...

    Thanks for looking at it.  As I expanded and realized how useful this could be, I changed some variables so they were a bit more obvious what they were.

  4. Untitled 2.layout

     

    This is what I was trying to do and how I got it to work.  I am a little confused Joe as you said these were all strings.  The math in the macro worked so how do I declare them numbers?

    If there is a better solution, please let me know.  I am trying to learn more.  This exercise will save me a bunch of time and minimize editing in the future.

  5.  

    2 minutes ago, Joe_Carrick said:

    Bill,

     

    I don't understand your last post.  

    1. Your Global Variables are all string values.  
    2. To perform math you need to convert to floating point
    3. If you are just looking up values from a table it should work.
    4. However, it appears that you are actually assigning new values to the Globals.

    What are you expecting?

     

    I was hoping on each project to define items, whether numbers or text. that would be used to populate my code analysis.  If the variables are in the same macro it allows me to do the math, etc.  I think I figured out a workaround....

  6. 1 hour ago, Joe_Carrick said:

    Global variables are persistent and can be accessed in other macros.

    • $TO
    • $CFL
    • $ep

    can all be used in other macros within the same session of Chief.  In your case:

      $TO -> "94 #Total occupants LSF"

     

    This is the output I get when I create a separate macro without the variables in it.  Basically I just copied the original macro with a different name and removed the variables and put them in a different macro

     

    "TOTAL OCCUPANTS =#{$TL}

    (LSC: #{LSC}.2.3.2)

    CAPACITY FACTOR = #{$CFL} (LSC TABLE 7.3.3.1)

    #{$TL} PERSONS x #{$EW} = #{$TL*$CFL} inches

    (#{$ep}) 36 inch EXITS PROVIDED = #{$ep*36} > #{$TL*$CFL} inches, OK"

     

    Basically I just copied the original macro with a different name and removed the variables:

     

    $TL = 94 #Total occupants LSF

    $CFL = 0.2 #Capacity Factor, Level, LSC Table 7.3.3.1

    $LSC = "37" #LSC Chapter for Occupancy

    $ep = 3 #Exits Provided

  7. I have found several online sources for RUBY, but I am confused on a few issues and how Chief uses RUBY.  I am trying to streamline my code analysis and there are variables that are used throughout and I always forget to change somethings that are used over and over.

     

    First question is how do you use the "inch" symbol: "  in a string?  I got (2) ' to do the trick (''), but is there a proper way?

     

    I put together the following macro for a portion of my analysis:

     

    $TO = 94 #Total occupants LSF

    $CFL = 0.2 #Capacity Factor, Level, LSC Table 7.3.3.1

    LSC = "37" #LSC Chapter for Occupancy

    $ep = 2 #Exits Provided

     

    "TOTAL OCCUPANTS =#{$TO}

    (LSC: #{LSC}.2.3.2)

    CAPACITY FACTOR = #{$CFL} (LSC TABLE 7.3.3.1)

    #{$TO} PERSONS x #{$EW}'' = #{$TO*$CFL}''

    (#{$ep}) 36'' EXITS PROVIDED = #{$ep*36} > #{$TO*$CFL}'', OK"

     

    It works (so far):

     

    TOTAL OCCUPANTS =94

    (LSC: 37.2.3.2)

    CAPACITY FACTOR = 0.2 (LSC TABLE 7.3.3.1)

    94 PERSONS x 0.2'' = 18.8''

    (2) 36'' EXITS PROVIDED = 72 > 18.8'', OK

     

    The problem I am encountering is the way I format.  I would like to be able to use the variables throughout the several pages of text including the bold paragraph headings. 

     

    First part:

    771145793_CodeAnalysis.thumb.JPG.51f37e921a261134d8df4ea809b0831a.JPG

     

    One good example is the Chapter of the LSC which is based on  the occupancy and I have 12 occurences of this hence, the variable "LSC" so I would like to declare that and just use it in the places needed.

    For this I created a macro %code_lsc_chapter% which is simply: "#{LSC}" and this seemed to work.

     

    My goal is to create a data macro I would edit for each job with comments for me to go through systematically with other macros to fill in the spot holder:

    $TO = 94 #Total occupants LSF

    $CFL = 0.2 #Capacity Factor, Level, LSC Table 7.3.3.1

    LSC = "37" #LSC Chapter for Occupancy

    $ep = 2 #Exits Provided

     

    The problem I am having is if the variables are in a different macro, the subsequent macros can't find them.  I have seen mentioned on the forum that if I put them in a text box somewhere and hide it off to the side it fixes this issue.  This is where I feel stupid.  How do I write a variable to a text box or is that the wrong solution.

     

    Basically I want to be able to use the data macro variables in other macros.

  8. 2 minutes ago, ACADuser said:

    Just remembered why I don't use the CAP on parapet walls. The cap pushes the top plate down in the wall.

    So delete the wall cap & use a molding line to construct the cap flashing.

    I really appreciate your input, this is a commercial job, however have several residential jobs coming up that will have some low slope roofs.

     

     

  9. 6 minutes ago, GeneDavis said:

    But I used to frame, so what do I know?

    I'm just asking for help, no need to be insulting.  Sorry, I do not know how everything is framed being a desk jockey, but got most of it down.  Other than the way it was presented I do appreciate it.

     

    I ALWAYS do my plans to allow the contractor leeway on details like this.  My attitude is they generally know much more than I do and I would be crazy not to give them discretion on how some things are built. My Goal is to figure out how to get this correct or as close as possible in Chief as I have this and 3 houses that will use this method.

     

    And only one of the images above are correct but after downloading and regenerating the wall framing they both show the truss being notched at a bearing plate.  So that seems to be the part I need to figure out at this point!

     

     Nothing like being 99% done with a project and having to regenerate framing and mess up all the things I had to correct by hand.

  10. 3 minutes ago, Kbird1 said:

    Perhaps you should of supplied the "This is what I want produced from the Start" and we would of said it can't be done auto... and you wouldn't be so frustrated....

    Perhaps I made the assumption that this was the only way to build this... and even included a sketch.  

     

    1463940551_FLOYD2.thumb.JPG.599bf867309eb212acef6c64219bbc1c.JPG