GerryT

Members
  • Content Count

    419
  • Joined

  • Last visited

Community Reputation

48 Excellent

2 Followers

About GerryT

  • Rank
    Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

2267 profile views
  1. I think Mr. Dermont's response is a little misleading. And, at the very least, I believe we can agree to disagree. When a symbol is brought into a plan, only the GUID ( or some form of it) is stored in plan within the Ruby class within the Ruby namespace. The attributes are not stored in the Ruby Namespace but are just class function calls to the plan data. This keeps the data private and read only. Therefore, it does not matter whether the sink is in open plan or within a cabinet. The memory is the same. You can test this by setting the sink's owner to a global, than equating that to a c
  2. It certainly is a part of Arial, etc.. which,if you do a web search of Arial code points, you'll see it listed. It does not show up in character maps because it is a non-printable control character. (Control set #1). Character maps usually only show printable characters.BTW: just because Ruby supports control set #2 doesn't mean Windows does.By definition control set #2 is optional depending on the software.
  3. Just checked -- Text boxes use the font selected. If the macro uses a code point out side of the font set, it returns a blank as expected. Labels use the chief blueprint font which about the same as Arial. It would nice if we could get the definitive answer from Chief instead of guessing? There is noway, AFAIK, for macros to select a font set or size, they only pass through code points.or encoded text. Still hoping that the MM will let us select font size? EDIT: It appears that the MM only uses Arial but will pass through the correct code point. This will
  4. IOW: upgrade to X12 and it should work OK. However, there is still a problem. Not all Fonts (Most Not) support all code points.It appears that If the font you are using does not support the UTF-8 code point that Chief will default to its Chief Blueprint font which is close to Arial in code point support. If not.it should, in that case return either a space or question marl, but instead, it does default to another font which can be confusing.. At any rate, in X12, you can cut/paste or use the alt keys or use Ruby -- all should work fine except for the missing code point thing whic
  5. FYI: Single line conversion is: x = "5 3/4" x = x.split.map { |r| Rational(r) }.inject(:+).to_f => 5.75
  6. U+2220 - U+2222 in Cambra Math
  7. Most likely it was copied from a previous upgrade. Change the path in preferences/general/ruby from x8 to x10
  8. From reading your posts, I haven't the slightest idea of what your trying to accomplish. Trying to understand why you don't just put the file in your scripts directory and let Chief handle the path automatically for the MAC or PC. File.read ($LOAD_PATH[0] +"test_1.txt") Eliminates need for any path. Note that macs do not use letter drives
  9. Was Removed because of a general lack of user interest and Chief's support for macros. I am no longer recommending macros in Chief but you may want to contact Michael or Joe who have simpler solutions. Here's new link if your still interested. Keynotes
  10. best option is to just create a framing schedule -- gives everything you want If you want to differentiate studs in a material list. you have to create a difference between stud objects and material skin is not recognized by the material list as a parameter. so you have to use the ruby objects. such as line type or some other unimportant parameter. Select all your new studs and change something into something. Add a object macro into the material list in one of the unused fields Referencing the changed parameter.. Right click and select "divide into multiple values"
  11. Not in practicality ? This is only possible in X10 but if you close the plan and reopen the sequence will re-number in a different order. So -- more trouble than its worth.
  12. Eastern time zone-- sent you a PM.
  13. There is no attribute for wall height in Chief as of now. You can check the available attributes for any object by selecting the object and using the macro 'ObjectProperties'. ( or load a custom list macro - easier. Generally wall heights are determined by using the room attribute finished_floor_elevation and ceiling_elevation etc. There is no default method to load or save Globals with the plan in Chief -- as of now. There are several workarounds -- depending on your preference & effort. The easiest to just put your Globals in a Script to be automatically loaded on t
  14. You can use either if you use owner.area, you do not need to set Context and can leave it at none. As always, the object must be selected or the macro must be in a label.( assuming reference is not used)
  15. You can't use 'puts' in a CA macro as it writes a string to the console and there is no console to write to. CA transfers the output of a macro to their display internally. Use 'p' instead. It returns 'inspects' instead of string. Also macros only return the last known value so using multiple 'p' or puts will not give a multiple line output. Your last string is the correct method of chaining strings for output although Using expression substitution , #{} is a cleaner method. You might consider using a polyline with label (avoids using reference)