Alaskan_Son

For this particular situation—heck, for MOST situation—I think your solution is much better than the one I posted.

Depending on what you're doing, you can put a very tiny partition down on the floor. Just make it 1/16" x 1/16" x 1/16" and place it up against the back corner of your bookshelf. This tells Chief there's an adjacent cabinet on that side and so toe kick will continue on just the one side. You can optionally place the Partition on a unique layer and turn the layer off, but even with the layer on, you shouldn't actually see it in any views.

You'll have some additional cleanup to do, but start by adjusting the Baseline angle to match the pitch of the roof plane that your roof-plane-in-question is intersecting...

I suggest you take a step back and learn to make it work with Polar because using your newly adopted approach will only work for objects perfectly parallel/perpendicular to the X/y axis. The other methods work for situations outside those parameters.

Just FYI, fr anyone else struggling with this, based on Mark's picture here, this operation shouldn't have worked since he's showing 45 degrees in the Enter Coordinates dialog. I suspect he has his Jump setting set to 12". Otherwise, he would be having the same results as Gene was seeing. We can't have both a Concentric Jump setting and use the Tab entry method on the fly. With Concentric, its one or the other. If you have anything other than 0 set in the Jump field, then you will be limited to jumping by that specific increment.

This step is an unnecessary redundancy that serves no purpose for this particular use case.

Don't drag diagonally, drag perpendicular to the desired reference line before you hit tab. Also read my note re: using the circular edit handle.

By the way, you can also simply click Copy/Paste and use the little circle shaped edit handle to drag out a concentric copy using the tab key. Again though, angle snaps need to be toggled on.

Edit>Preferences>Behaviors>Concentric>Jump is one easy way to ensure you get the desired offset, but you should also simply be able to use the tab entry method so long as you have angle snaps toggled on.

It's because the Leader Line tool always obeys the settings for the text object that it is created for. In the case of Rich Text though, the Border settings are the only place to set line style parameters.

That linestyle is being inherited from your Rich Text Defaults>Appearance>Border

2 quick suggestions: Use the term Default Set in your posts. Its just a little confusing when you use the term Annotation Sets or Annosets since those terms were changed quite a few verisons ago. You don't need to create a whole new Default Set. All you need to do is change the Dimension Default being used for your Saved Plan View. Of course you can create a whole new Default Set, its just not necessary in most cases.

Auto Exterior Dimensions Should automatically remove and replace any previous Auto Exterior Dimensions unless you have previously edited those dimensions in any way. Per the Help files, any edited dimension "...will be marked as edited, so if Auto Dimensions are later regenerated, your changes will not be lost."

Agree

I agree. It would be nice to have separate control over the polyline and the polyline hole. In fact, it would be nice if we could even control specific edges independently.

Try this next time (a small upgrade to the brightly colored material idea you already suggested): Open up Plan Materials and Select All. De-select the material in question Click the Merge button, click Edit, click on the Properties tab, change the Transparency to 100%, and click Okay. Click on the material in question, click Edit, and set a very bright color for the Material Color on the Pattern tab. Open a 3D view, set it to Vector View, and Rotate your model to you find what you're looking for. Click Undo a couple times to get things back to normal. NOTE: Using Vector View isn't necessary and actually won't work in older versions of Chief either, but I find it easier on the eyes than using a Standard View.

I don't think we've actually ever been able to do this Joe. To get the hole to have an invisible linestyle, you have to change the linestyle on the polyline itself.

Find in Plan would do nothing to find those materials used in Defaults.

Your deck wall is just out of alignment by about 1/16". Move it over so that its right on line with the adjacent wall and you should be good.

That's because the tutorial is located in Chief's Program Files...a location you really shouldn't be playing around with. Your $LOAD_PATH should point to a user folder (probably the folder it was already set to). I would suggest you just forget everything you have read about using the tutorial file and set your $FILE_PATH back to the default "C:\Users\Whatever Path\Chief Architect Premier X14 Data\Scripts" folder and/or your desired Z drive folder.

Changes to many of your Preferences do not take affect till next time you start the program. This is true not only of your Ruby settings but of other settings as well.

By the way, you don't have to change the load path at all. The require method can take an entire file path as an argument as well. OR, you could even optionally set your $LOAD_PATH with the same macro that requires your rb file that way no one even needs to change their preferences. Any machine that opens the plan would get the load path set automatically.

This has been pretty clear to me from the start...at least if my understanding is correct: The idea seems to be that macros can be defined and edited in a single source file so that any changes don't have to be made in every plan and on every computer. I think its actually a really good approach for offices with lots of templates and/or lots of users. In fact, using this approach, an office could drop one single macro into every template plan. That macro would require/reference the same rb file. Within that single file, a company could hypothetically create ALL their own custom macros as methods. Modify the source file to include a new method and voila, that method/macro is available to every user and in every plan. Realize something needs to be tweaked? Tweak the source file and every other instance gets tweaked accordingly. It makes solid sense to me.

Lower left hand corner of your dialog boxes…Number Style

There's no good reason to be placing code into the tutorial.rb file in my opinion. Its just a messy and confusing kludge. All you're actually doing by placing code in the tutorial file is bypassing the require line because Chief is pre-programmed to automatically load that tutorial.rb file. You can easily replace the functionality by just using require in a text macro of your own though so you don't have to fool around with defining your methods in the tutorial file. Just create and display that macro somewhere in your template plan and all the methods defined inside your appropriately required rb files will be loaded into global memory just as if you had placed them in the tutorial file. Or require the desired rb file(s) inside specific macros. Either way, just load them yourself (using require) instead of using the tutorial file workaround.