glennw

I love your work Yusuf!

You should be able to dimension in an elevation view. It is probably one of your dimension defaults and/or annoset settings. Post a plan and an explanation of what you are trying to dimension.

Rod, The tutorial says "Convert Polyline" NOT "Convert TO Polyline".

I am not sure there is a Convert to Polyline tool. What are you trying to do? Convert Curve to Polyline Convert Spline to Polyline Convert to Plain Polyline Convert to Polyline Object Convert Polyline

Joe, you got it - sort of. And that's how all my normal dimensions are formatted in Chief. Except for site plan dimensions and notations which would normally be in meters (eg: 24.476m or 6.5m). But...a lot depends on things like context and the magnitude of the units. But, to answer your original question - we would not normally refer to the perimeter dimension of a room (why would we need to?). In most cases, If we were notating or dimensioning the size of a room (width x breadth), we would use mm (3600 x 4200) - on say a con doc. However, if were talking about the same room, we would say ("3.6 by 4.2 meters"). If the same room was in a sales brochure it would probably be indicated as "3.6m x 4.2m" Simple as......

Joe It looks like it going on Graeme's (Kiwideziner - from NZ) post #12.

Joe, Not in Oz. We would never use a comma as a separator. We could have 1, 2, or 3 decimal places, depending on the accuracy needed. And we would usually drop any zero's from the end. So 14.112m would usually do it, but quite often the m would be left off because it is obvious that we are indicating meters. And same as Graeme in the post above.

Probably no need to do that, this is already available. I note that you are talking about manual dimensions - not auto. Have you checked what Dimension Default your current Annoset is using. My guess is that your current Dimension Default is not set to "Interior Wall Centres" in your current Annotation Set.

View menu...Scrollbars

Micael, We are talking about the Description column. You can change the Description in the Components dbx for all the door types except the Pass-Thru. There is no door "component" (because there is no door) for a Pass-Thru as for the other door types, so there is no door entry to change the Description. Like Joe says, you will need to use another column like Comments.

Shane, As I said, open the Component dbx (Edit toolbar) for the pass-thru and in the Description column, change "Pass-Thru" to "Security Curtain". The Description column in the window schedule will now say "Security Curtain" for that Pass-Thru.

Shane, Window Schedule dbx...General Panel...Objects to Include...scroll down and check Pass-Thrus. You can change the Description in the Components dbx for the window and that will then show in the Description column of the schedule instead of Pass-Thru which is the default.

Scott, A bit hard to control exact slope using a terrain. ie, making it 10deg slope (2 1/8 in 12) And I think having roofs inside rooms with other ceilings and roofs above is asking for trouble

I would use a roof plane - very straight forward and controllable. You can shape it and slope it any way you want. Copy it to a blank plan and convert it to symbol and copy back into the original plan. By making a symbol of it, it won't be treated as a roof plane and thus it won't cut walls, etc. Only takes a couple of minutes to build it.

First, create a Terrain Perimeter. Instead of using a slab for your pitch, use a Polyline Road. You can then use Road Stripes for your lines.

Yep, I can confirm all of the above. It seems to be a time out setting.

Sounds like you may have an object located a distance from your building. Have a look around.

Am I missing something here. Why can't you just build a normal roof with a boxed eave. Measure the distance between the eave soffit and the ceiling. Enter that distance in Raise/Lower from Ceiling Height.

Michael, I am a little confused by your last couple of posts, but I think I may understand. And I think you can do what you want - if my understanding is correct. As I understand it, you have different template pages for you different plan "sets" in layout. You have pages numbering sequentially within each plan set (by using 6# for the label). But what you want to do also is number every printing layout page sequentially over the whole layout which includes all the individual plan sets. To do this, you can use the %page.print% macro in a text box on each layout template page. This will number ALL your layout pages from 1 upwards and will ignore your template pages and will be independent of the page numbering within each of your page sets. I highly suspect that I could be way off the mark with my understanding of what you have and what you want to achieve. If so, can you explain in a bit more detail, or better still, post a layout and the referenced plan with an explanation of what you want. At first reading it would appear that your first post was answered by Jerry in post #3. Or...I could do a quick Skype session with you if you would like me to take a look at what you want.

Michael, As far as I know, you can move a Place Point, just as you can a Point Marker. Double click on the Place Point and enter the location. MicketToo, It's quite easy to include or not include the Point Marker at the insertion point of the block. Place your Point Marker and Copy and Place In Place. When selecting the objects to make up the block, just click once on the 2 Point Markers and only one will be included in the block. The other copy in the same location can then be used to snap the insertion point to. If you use a window selection, you will initially get both Point Markers in the selection. Just come back and Shift Select the Point Marker and one Point Marker will be deleted from the selection. Then make your block and snap to the Point Marker for the Insertion Point. http://screencast.com/t/wZSBxAeoP

You could have 2 window with one stacked on top of another and/or a window using a different Stacking Level.

OK, I can do tomorrow. Saturday 9am here.

Perry, It seems to be a W10 problem, although I am no windows expert.. I googled it and it is a common problem. Whatever, it is now fixed with no ill effects.

I'm up for it.

Yes.