GerryT

FYI -- macros and RUBY were introduced with version X3. After that, Chief stopped development and made only perfunctory changes. Basically the X3 version hasn't changed much. I made a introductory set of videos for X3 which are now somewhat out-of-date now. But the X3 Chief videos are decent enough. You haven't seen much practical examples because there just aren't many practical uses of this feature. Chief pretty much "crippled" its use and limited it to Text and labels. There really isn't any reason to hide functionality since it's minimal. IMHO -- changes necessary to remove the "roadblocks" to practical usage are also minimal, which tells me that that Chief is not interested in extending this capability. Probably not enough interest??? There are a number of workarounds but most involve "global" memory with very limited benefits for the effort. Basically Chief has depreciated this feature -- again no interest. if you have any specific questions I can answer, but most answers will be Chief deliberately prevents doing that. For now macros are mostly a dead end with only limited usage -- by design.

That's just a Stock photo -- but nearly Identical to a terrier I had that has since passed on - Good memories with good friends.

I have current versions of each. If you tossed Revit LT you don't even want to look at TurboCad. TurboCad's layouts are limited but adequate. SoftPlan has excellent layout capabilities - comparable to Chief. In other areas, except material control in SoftPlan, Chief is more intuitive and productive. It has all the necessary CAD capabilities to produce efficient construction documents without requiring another CAD program -- so you can save some money there.

For item #1 just use the the RubY IO class -- i did a video on that about 4 years ago -- you can also load construction notes by cutting from selected parts of a word document allowing you to update your construction notes external to Chief in word doc(s) and then have them update to all your Chief plans or layouts automatically. For the second item, Ruby can not read Text boxes in Chief, but you can paste text into a macro box and extract from there or re use that macro as many times or where ever you want. For the third item, you can only do that by ID ing the objects,(workaround ) which is more trouble than worth right now as Chief has prevented this direct approach by way of a previous revision in labels. Also Ruby has no access to any Commands. There is no way to directly read parametric data in Ruby. Chief is not interested in providing those features so don't expect it!! We have been asking repeatably for these features for years -- since X3-- and the response has been NOOOOOO WAYYYY!!

I agree 100% I own a copy of Softplan 2014 and have experimented with it quite a bit. The approach of the two programs is very different. So it basically comes down to what you might be comfortable with. I also don’t agree that Softplan’s CAD tools are better, just a different approach. Chief’s approach eliminates the need for a wide range of CAD tools as there simply not needed. People tend to migrate to the program that aligns with the services their trying to sell and ignore everything else. For example, Softplan is much stronger in material control than Chief, so you’ll find that few Chief advocates here use its material features very much. Same is also true with parametric data access. However, Chief’s framing tools are much better—but limited in scope. OTOH, Chief’s 3D graphic design tools are much easier & intuitive to use, so many designers here migrate to this area. Chief is famous for its “workarounds” which require a combination of tools in ways not obvious. Softplan is more stuck in the 1980’s Cad philosophy of one tool for this and one for that. Chief has a more unified approach. An advantage in Chief is its Cabinet and Kitchen design features which are superior to Softplan. But that’s not important if you are not selling that service I strongly urge you to get a demo copy of both programs and do one of your typical designs in both. Take a close look at the videos on YouTube for both. I also add that Chief’s support, if you subscribe to SSA, is much better. IOW, the best program is the one that aligns with the services you want to concentrate on. You can only determine that by working with both.

Once you send to layout with auto on (First check box) the label stays in the "below line" field. Uncheck Auto and erase that field. Leave auto checked for callout size or set manually.

FYI: I don't see any macros --- but you have automatic checked (below the line) in your callouts ,which is the default. This will pick up the layout label name for the layout page you sent the elev to. Only pickups on the the original send which is why you don't see the same effect if the elev are already there. Not sure I agree which this behavior? Uncheck auto or change you labels to something smaller.

Sheldon: You don't necessarily have to trace as your survey has MOST of the necessary data. Just use the input line and input arc tools. I found that your survey does not close, probably because the arcs are not truly tangent to their starting points and no cord direction is given, but it's very close. Either the surveyor omitted cord direction or just approximated. You can close the survey by just extending a line. The Lengths will be within a few tenths. Chief is very finicky about connecting curved lines so try the connect line tools if you have trouble there. You'll get a area measurement if all are connected, then convert to a terrain.

"Ghosts in the machine. " FYI: There is a bug in the implementation of macros, particularly on page 0 (or any template), whereby following pages may execute before page 0 so that macros, may,in effect, get lost. This is also sometimes evident in using reference macros. I expect that saving or some minor change made just repacked the sequence of objects which allowed it to start working again -- meaning it also could return. Which is why I don't believe that the present implementation of Ruby macros could be made reliable enough as the basis for any API or any other extension.

Your request could be interpreted in a number of different ways. Is this what your after?

Glenn: Eactly. But looking for automation that can be drawn onto a wall detail. ML nice but not a biggie as I can allways enter manually along with a bunch of other stuff.

My idea of applying thin surface members of 1/4 -1/2" normally out of scored MDF or drywall to be applied to curved arches and ceilings that would also list correctly to the material list. Can do the same with concentric polyline solids but a pain to create and size-- I want to automate in order to give better details- which I don't do -- just now copy the vendors DWG as a detail. I think it would have better use in trying to depict various curved ceilings. Maybe just a framing member that can be curved with the"change line/arc" tool.

Glenn: Not sure your interested -- But: You can use a framed wall to handle the framing. Just copy and place the material region on both sides of the wall-- don't need the "opening no material" -- just delele all material layers in the material region-- will show only as a line(s). For the framing -- frame as normal, make a copy of one of the material regions and convert to polyline -- cut and locate the polyline in the wall detail to use as a template and adjust/delete/edit framing as needed - would be nice if we had a curved MDF tool. Gives you a framing detail + list to material list.

Because you originally attached to a wall, it stays snapped to a wall. Change the symbol to floor mount in the library and place in the middle of the floor. It will then rotate in xy. but not zx, zy (use symbol DBX). I guess this could be considered a bug -- Chief is doing some funny things with electrical symbols?

FYI: Changing the symbol from wall mount to floor mount allows rotation just fine for me. As a symbol, it can only be rotated in the xy plane. To rotate in ZX or ZY you must use the symbol DBX and rotate around the proper axis. Also you can not stretch the symbol since it appears that electrical symbols do not allow stretch Hotpoints -- at least this one?. Change to a fixture rather than a electrical symbol then you'll get your stretch points in which you can set your stretch planes. . You don't want to stretch anyway because your lights will be spaced too far apart. Just put two symbols back to back. resizing would just increase the size of the lights which you also don't want. Not sure why you don't post an example which would get an immediate answer. At this point, I'm guessing that Scott is just shaking his head. EDIT: --you can build your own cable lights with the # of lights you want and the lengths by using the track light heads and cylinders.

Something you probably need to "play with". Zipping and posting the plan or an example would get you an immediate solution. Generally -- Open the symbol, under options, and change from wall mount to floor mount. Then set the offset from floor as you want in the DBX and move where you want. Change the angle in the symbol - probably Y axis, to what you need. You may need to relocate the origin. Not difficult -- but confusing if you haven't seen it done before.

FYI: -- All of the info you asked for is in the component list for each Cabinet. if you don't like the descriptions, you can edit them, but be advised if you then subsequently change a dim, that edit will be erased.The component list is directly copied to the material list, so you'll get a complete listing there. If you want more info add subcategories to the component list. Most of the info you are asking for is not avail in the schedules but you can add manually via sub-categories The sub-categories will not be erased.-- Check Chief's videos. Finally some generic info is available via Ruby macros -- but that's another tune?

I agree and I rarely use any tool(s) the same way all the time. This is just another possible option evolving (maybe overlooked) from several suggestions in the past. My biggest complaint about Chief is that they tend to target their tools to specific instances and ignore other opportunities to expand the versatility of the tool. Programed limitations preventing huge benefits. A niche tool or just the expansion of the Material Region would be welcome.

Another approach to wall niches -- just a summary of previous suggestions http://youtu.be/Er7l8fs_Iko

Yep that works-- but only in one direction since the bounding box cad block can not be offset.

Hmmmm - I suppose by that reasoning that features such as: Material Lists, Ruby Macros or Symbol creation will also be supplanted in X7? Perhaps a better explanation would be that the features of this tool will be incorporated into a more versatile one? Lets improve not remove :)

Pretty much -- But any Chief field that is editable & standard is overwritten. SOOO - if you change the description,etc. it will get overwritten too. This is actually an improvement as in the past everything was dropped, and rebuilt. Sub-categories are not overwritten -- after some long complaints!!Progress???? -- (But their still not listening) This gives me some "heartburn" as the Code field is accessible from Ruby macros, which I could use as a ID field, but it gets overwritten too and is therefore useless.

Pick your poison. I've got enough Junk in my library that I prefer one size fits all OTOH -- I personally believe in the cardinal programing rule that you NEVER erase any user entered Data - at least not with out a warning.

OK -- Here's the problem with that - You add a comment and save to library to reuse. You then bring in but decide the dims are wrong so you change them .. Your comment is erased. Better to use Sub- categories.

Still somewhat useful -- I never knew was there. I do a lot of wall detail editing in "wall detail" and usually wind up using the surface delete to see the final. -- PITA. At least someone at Chief is "thinking" about framing? This tool should come in handy when trying to view lintels and corner blocks. BTW -- Chief's framing tools are still the best and easiest to use -- too bad yous guys don't take advantage of the opportunities to expand.