Joe_Carrick

I don't think it's a bug because: It's possible to have more than one Layout open so there could be confusion. The Section/Elevation could be sent to different pages simply because there are more pages in one Layout For which Layout should the Callout report the page? If only one Layout is open then the Callout in the Plan will report which page the Section/Elevation is on. OTOH, if no Layout is open then the Callout basically has no way of knowing what page to put in the bottom of the Callout.

Thanks Rene, Flagstone 4 worked great with just a tweak of the color.

It's worked for me - many times.

When someone incorrectly posts a question in this Forum Report it with a request to the CA Moderator to move the thread to the Q&A Forum. It's that simple. Telling the OP to delete and ask their Question in the correct Forum almost never achieve that result. That's my TIP for today.

Anyone have a texture for random shaped flagstone? Basically I want a large area that would allow random sizes and shapes.

Thanks Mark. I'm pretty sure it was version 10 But maybe it was as late as X4. IAE, it was in the prior Chieftalk and I don't think that post is available any more. IAE, The Cabinet Tool does have a lot of modeling capability.

I reported this - specifically for Fixtures in Cabinets - but it's valid for fixtures in general. There's no edit handle and if the label is suppressed you can't even set an offset in the dbx. Please report this so it will get more attention.

My Title Block is about 4-1/2" wide. That gives me enough room for the Layout Table (Sheet Index). I also have various Layout Templates for wider sheets - some of which are custom: 24x36 24x42 30x42 30x48 36x48

I include the Layout Table and Revision Table in each of my Page Templates as a part of the Title Block. That way they are automatically on every sheet of the Layout.

It's always been that way and it's in the Help File.

IAE, That's being used as an exhaust vent from the Tankless Water Heater. It isn't a Water Supply Pipe. Is there really a reason you need to include it it the model?

No

Does anyone have a typical structural detail for shear transfer from roof to wall with nailing, etc they would be willing to share? Our structural review her in San Diego wants such a detail so the contractor will know exactly what to do. This is a simple 750 sq ft 1 story building with conventional lumber framing. CRC Fastener Schedule isn't sufficient for this plan checker. Thanks.

You could also try reducing the Text Margins. That also solves the problem.

So here's one other thing to check when you have a seeming lockup. Look on the Taskbar and see if there's a modal app (popup) running that's not visible on the screen. It might be asking for input but you can't see it because it's hidden behind Chief. If so you can bring it to the forefront and answer. This happen sometimes and we just don't recognize that it's the problem.

It's a bug that's been reported. The text line spacing is being affected by the top and bottom margin spacing. Converting to RT fixes it - until CA fixes the bug (assumedly the next release.

Not that you can see, but internally within TMM a loop can be entered. That evidently is what has happened in this case. It's always best to test that a variable is initialized to a value that works with any condition the script attempts to perform. ie: <=>+-*/, etc. If an error occurs within a script it's possible to initiate an infinite loop - particularly when using TMM which tries to determine validity. In this particular case I suspect it's not the macro itself that has the offending loop. Rather it's probably TMM that's caught in a trap.

It's not so much that it can bring CA down, just that it has control of the Application and doesn't allow any other input. But of course the OS can terminate any process - ie: via Task Manager. In this case the Ruby Script is running under Chief Architect so that's what has to be terminated.

Hi Mick, I took a quick look at the macros as listed in the original thread. They're very poorly written with no checks to make sure the variables are initialized properly - or providing a way to exit gracefully. I would not import that into my system for exactly the reasons I stated. One of those - or maybe both - have the potential to enter a loop with no way of exiting. I'm not going to try to "fix" the problems - just beware installing such code without knowing what sort of trouble it can cause.

Chances are that you have an infinite loop in the macro. When you open it in TMM it tries to execute the macro but it never gets out of the loop so it can't exit the macro and release the CPU. It may be that if you first select an object that uses that macro before opening TMM then the macro will exit properly. Proper error handling might eliminate the problem. It could be as simple as an unitialized variable.

Here's one I designed

It would be best to just use a Cabinet and modify it in the dbx to look the same as the Kohler Vanity. The Cabinet Tool has all the features needed to create almost any Casework. You may notice that all of the "Cabinet Manufacturer Libraries" only have the materials, colors, etc. They rely on the Cabinet Tool to provide the basic structure. Chief had and maybe still provides a "Cabinet Symbol" tool - but it's not at all easy to use. Using the Cabinet Tool provides a much better method. Once you've configured a Cabinet you might want to use again - save it in the Library.

Correct. But once you've numbered them you can link other Plan Callouts to the view and there's a macro to fill in that number.

Hi Rene, Do you include your toolbars with this? Are they needed to make the system work? If I purchase the Standard can I upgrade to the Pro for just the difference of $200?

Correct. It's whatever the name is in the Project Browser