-
Posts
422 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Everything posted by GerryT
-
I strongly doubt that you can copyright concepts that have been previously Demoed by someone else? You can only copyright specific code and what you are describing is so general and obvious that I doubt that Chief would tolerate it. It's like trying to copyright a "door" or "your fired". Although, nothing would prevent a license agreement and/or NDA. INMNOHO. However, you may not be aware that Ruby macros can be encrypted or compiled which might be a better path. But you would have to convince Chief to allow that, which shouldn't be much trouble since you're now one of the "chosen".. But I wish you good luck and expect that most would prefer this -- Good Luck- I'll help in any way I can -- No Charge!!.
-
Can't tell from your image or description what you are trying to do? But a owner object macro can only be used with a selected object as within a label. Polylines do not have labels. A reference macro can only be used in a textbox with arrow leader. If you use owner or reference in the wrong application, you'll get a error -- unless you "catch" the error. Need more info.
-
Again a fundamental misunderstanding b/c Chief is soooo inconsistent with Ruby applications. You can not use ruby macros in a text box within rooms b/c Ruby can not recognize a room boundary. you can only use Chief's macros there. But if you put the ruby macro into the room label or the default label, it will work OK, The reason is that a object has to be preselected via the label or reference in order for Ruby to read that objects attributes. But for Rooms only, reference will not work at all, only labels work there. This is by design. This why the console works, if you preselect the room but a text box with ruby will not work for rooms.
-
OF course it can, Custom tables accept macros -- You just have to use global memory. We've had this capability since X6. But in most cases, if your just doing one plan -- more trouble than it's worth.
-
Yes -- that is part of the Ruby language and can be used within a Owner or reference content macro.
-
conditioned and unconditioned attributes are available for rooms within Ruby. So the above is possible in Chief and I have demoed exactly that. However, it's more complicated as you additionally have to consider if you need the total structure or just one floor, And you need to purge out deleted rooms, this makes this somewhat complicated in Chief but still doable. BTW - Archicad's zone approach is much easier except that you cannot subtract areas only add them, so any area analysis is impossible outside of a programed plugin. Pick your poison?
-
Just use the "clone" method that I mentioned before. Downside is that it will be erased when you exit meaning you will have to re-establish whenever you re-open the program --IOW there is no alternate as Chief's management seems to have closed this discussion down at least on their side -- So much for the wheel theory- HMMMMM?
-
1. check evaluate 2. object to "referenced 3. Use in a reference text box pointed within the polyline 4. get some training or view the SSA videos -- Chief just makes the simple incredibly confusing and convoluted.
-
Larry: You seem really curious about Macros in Chief, but lack a fundamental understanding of their "limited" usage in Chief? Its really not complicated, but without the basics, it's cumbersome and confusing to understand. Rather than continue to struggle, And waste time with things that aren't possible and not likely in Chief, I suggest a 1-2 hr basic review of Ruby in Chief. If you like, I'd set up a "go-to-meeting" session to cover the basics -- might save you you much future wasted time in understanding what you can and can't do with macros in Chief. If interested, email me through Chief's message system with your e-mail and a proposed time and I'll set it up as a one time freebee. And, of course, any one else interested? If not, you should at least review the SSA videos as a starting point. Just search on Ruby or Macros.
-
Interesting - I had the same opinion, initially. But realized that you have to dig much dipper to accomplish similar tasks in Archicad vs Chief The two programs are completely different in philosophy. In general most task will take longer to do in Archicad vs Chief. But you save in the end because everything just works and is well thought out. So for "cookie cutter" residential Chief will shine. Step outside that and Archicad usually will have a solution. I don't think it is possible to evaluate Archicad in a thirty day trial or without formal training. Most shops that use Archicad also have the resources to hire a dedicated administrator. So from a overall productivity standpoint, Chief is faster out-of-the-gate. Archicad is definitely long term. The proof is categorically in the market share . That said, Chief has the basis to surpass long standing deficiencies in Archicad, notably in Material management and data access. The gap in BIM (IMNOHO) is mostly BS. Unfortunately Chief's management is just to shortsighted and reticent to see it. door_1.zip door_x6.plan
-
MM - Macro Management DBX JSON - Java Script Object Notation Language - That is the format that Ruby macros are saved in Chief when you export/import macros. Basically you can ignore this as Chief just takes care of it.
-
Exactly - Why Chief would invest thousands of manhours in a feature than cripple it to the extent that it is made mostly unusable is the eternal mystery? Never heard a credible explanation from Chief yet?
-
AFAIK Slider behave the same as leaf doors and are limited to only two doors in a frame. Chief does have some Nana wall panels but those are symbols and do not carry any (much) info. Maybe some one else can help?
-
Nope, Nope, Nope Ruby attributes have to be used within Ruby Macros. Chief macros and Ruby are different but Some return the same info. Chief's macros can not be changed.. Attached is a macro that may get you in the right direction -- if you need more ask? Add the macro to your MM DBX than use as a label macro. door.zip
-
YES/NO Ruby does have a attribute "is_double_door' which you can use to test if double door leaves are present. The width attribute, however is only the total door(s) width, so if a double door is present, just divide by two. Chief does not do multi-leaf doors other than symbols and those do not have the appropriate attributes. if is_double_door == true then etc. etc. else etc., etc. end
-
AS I pointed out, if the autocad dwg did not draw as 3D lines (i.e. z height) they will not import as elevations. Also sometimes the designer will use small line sections than block the same. There are many other scenarios so need to see the dwg. Generally you can select and convert them somehow. Just zip the dwg file and attach as a zip file. Also make sure your terrain origin and the dwg origin are the same otherwise the lines may be in the outfield. -- No solution for lack of surveyor.s data, You'll need to get the angles from him for the plot outline. Most local authorities require this data unless of course you run into a incompetent clerk , which, of course, almost never happens?
-
The survey data in the PDF does not include data for the curves such as start angle or CH angle, without which the plot can not be closed in Chief. I suspect the pdf was generated by a survey program which would interactively find these angles by trial. You should get that data from the surveyor as it is probably still in his instrument. The contours can be brought in directly from the dwg only if they are continuous 3D lines. Otherwise you can just select and convert to elevations in Chief. Attach the DWG????
-
There are always alternatives. Just put everything together. 1. Use a door or window as the "hole" 2. use the "build framing" edit button to frame around hole. Retain framing or modify. Unfortunately, Chief only frames square "holes' so you may have to modify to add diagonal bracing. But not hard while in wall detail. 3. draw over top of door hole, the exact shape material region you want to get the niche outline.Open material region and delete all material layers. You may have to turn on framing to get rid of USB place holder. 4. delete door/window hole. 5. 5 minutes max -- did same video a months ago. The advantage is that the framing is also detailed and you don't need to rely on the the framer to guess what you need?
-
X7 Rt With Macros Connected To Closed Polylines
GerryT replied to Joe_Carrick's topic in General Q & A
I would say that some change was made or maybe just me as every time I test I notice something different. It would be nice if Chief would verify when they work in a area? I've noticed that the reference line now has to be connected to the outline for primitive 2D shapes, and still anywhere within in a 3D polyline. It does seem a little more stable now? Also seems to be stable when pasting from another open plan -- maybe just me? -
Thanks for the info Guys. I'm not trying to convince anyone of anything and frankly could care less -- just trying to understand a possible new better method. -- Go to it Guys!!
-
I guess I don't understand why adding and editing a plant label is more straight forward than just directly editing a table which is why I suggested a video which you said you were into now. Always looking for faster better?
-
Mick: plant schedules are " live" only for plants which are only place holders in this application. No direct correlation at all here but sounds good.You may want to try out Chief's capabilities?
-
Joe: sounds like you're describing "keyed notes" which is relatively easy and more direct using macros and tables. Maybe I'm missing something. Still puzzled as to why so many prefer the complex/limited over? Video?
-
These type comments have always puzzled me? Chief already have the capability to use and import tables created in WORD with the ability to be filled in, edited, formatted, and save/reuse in Chief. I know you are aware of this -- just wondering why the phantom plant method is preferable? Seems like it would just "junk up" the plan?