Markus Barrera-Kolb

Vincent, all I did was make a worksheet with a database row returning the record format that I used for my custom title block. Before automatic drawing coordination, I could then edit the sheet numbers right here, though not the drawing titles, since I use multi-line titles (I could enter a title in the worksheet, but then it would only be a single line title). With ADC, I can no longer edit the sheet numbers in this worksheet, but can now edit them in the sheet layer pallette as well as the title block dialog. What this worksheet still is quite useful for is quickly editing the 'drawn by' and 'sheet X of X' fields, rather than having to do this through each sheet layer's title block dialog box. To obtain these record fields in the worksheet, just select the appropriate criteria for you database row and then enter the formula for the desired record field, in our case "=('whitney arch D TitleBlock'.'S_sheet title#')" You'll notice that I'm not using the ADC sheet title field, since I still want to use multi-line titles. I think I'll make a feature request for support of multi-line titles using ADC -- I don't see why that wouldn't be feasible, since I can list multi-line titles in the worksheet; I just can't enter multi-line titles there. By the way, I'm not using this as the drawing index on my cover sheet, though I guess I could easily modify it for this purpose (haven't used the Create Drawing List function yet).

Vincent, I left a very lonely post about this a little while ago -- I found that contrary to the documentation, it's actually an _SN suffix not prefix, as you also indicate. The other thing I found is that, again, contrary to the documentation, multi-line sheet titles are NOT supported, even when adding a pound sign to your record field suffix (i.e. "_SD#") -- Automatic Drawing Coordination will simply strip out the extra lines. Furthermore, while edits you make in the title block dialog box will indeed show up in your sheet numbers & titles and vice-versa, if you (like me) make yourself a worksheet that summarizes your drawing set, you will not have two-way functionality, i.e. you won't be able to enter new drawing numbers here. Hope that helps. Cheers, Markus

Thanks Pat, that's a great script. Funny enough, Julian Carr just emailed it to me as well, after I'd asked him about WinDoor record fields. I'm sure it'll be useful on more than one occasion... Cheers, Markus

OK, I've finally upgraded to 2010 and ZCENTER does now work, although oddly I'm having to divide the elevation by 12, even though I have the field set to use the doc's default dimension unit -- feet & inches -- but that's no big deal. Now I'm trying to extract the ID Number in a database field as well, but can't seem to find a record field for it. Is this a piece of data that is embedded in the PIO that you can't access in a worksheet? The Stake record format does have "Stake #" and "polyline ID", but those are different than the "ID Number" that you can set in the Stake Object's OIP. Cheers, Markus

Most of my wall types have a structural component, e.g. the studs, and finish components, e.g. the drywall. On our floor plans, which we want to keep clear and simple to make it easy for the contractor to lay out the framing (the plan's main function in the construction set), we'd like to turn off the finish components and just show the stud lines & hatch. However, when I turn off the exterior & interior finish component classes, the hatch disappears from the structural component in certain places, usually bounded by certain wall intersections and inserted windows or doors. In most other places it shows up just fine. Is anyone else encountering this? Since we differentiate between existing walls and new ones by hatching the new walls, this is an important function. Cheers, Markus

DOH! Thanks Jonathan!

It would be great to be able to turn off line thickness zooming in the snap loupe -- after all, you're using the loupe in order to tell things apart, and when lines are thick, that's much harder to do! Kind of undermines the usefulness and effectiveness of the tool, IMHO.

Raymond -- thanks a bunch, that's exactly what I was looking for. Sorry I didn't phrase my question more clearly. Cheers, Markus

Does anyone know what the pref number for "Display Screen Objects" might be? I'd like to write a script to toggle it, so that I can quickly draw 2D objects while in a 3D view in order to generate new 3D objects, but then turn off 2D display again with a keystroke. Thanks! Cheers, Markus p.s. is there a place in the new documentation where the pref codes are listed?

Unfortunately yes. Don't really know what to do about it. Might it be something between the OS and VW that's not quite copacetic?

Yup, have definitely done that.

The section markers that I've placed with the "Section Viewport" command and that I've set to Helvetica keep reverting back to Geneva (which I unfortunately find exceedingly unpalatable) everytime I reopen the file -- is anyone else having this problem? Sorry for the barrage of questions, but I'm just getting up and running with 2010, and I think I'm a magnet for weird software behavior... Cheers, Markus

Automatic Drawing Coordination is something I'm excited about, but it seems that multi-line sheet titles may not be supported. Has anyone figured out how to do this? The user guide says to use an "_SD#" suffix for the sheet title record field in your custom title block, but when ADC then links your nice, descriptive multi-line title with the sheet title in the sheet layer navigation palette, it strips out the text on the additional lines, bot in the palette AND the title block -- at least that's what I'm encountering. Has anyone else gotten this to work? Thanks. Cheers, Markus

I'm working on my MacBook 13" and have run into the following problem: when I go to edit my title blocks, the dialog box is too large for the screen, and I can neither get at the top nor the bottom of it, whether to reposition it or click OK (I can cancel out using Escape). I've tried it on my desktop and with an external monitor and discovered that the dialog box cannot be resized -- there is no resize handle in the lower right-hand corner! Seems to me like its size is simply determined by how many fields you have in your title block and whether they are single-line or multi-line fields. If it's too big to fit on your screen, it seems you're just SOL. Why wouldn't NNA make it resizable with scroll bars?!?! Does this mean I simply can't edit our standard office title block on my laptop without an external monitor? Cheers, Markus

Well, unfortunately that didn't do the trick, so I'm stumped once again. Another call to tech-support?

Hmm, I wonder why they decided the section viewport marker didn't need to be fixed... Is there a way to tie the 2D marker from the anno toolset to a section viewport?

Perhaps it's just me, but I couldn't get the SN_ prefix to work for my custom title block -- however, using an _SN suffix seemed to work fine for automatic drawing coordination. This is contrary to what the VW2010 documentation says (see attached screen shot). Unfortunately it doesn't seem that two-way functionality exists if you pull the record field into a worksheet, for instance for summarizing your drawing set; if I enter a new sheeet number into such a worksheet, the number is updated in my custom title block, but not in the sheet layer name or the linked viewport labels (if I change it using the title block's dialog box it works fine in both places). Anyone else? Cheers, Markus

I spoke with Jay Wilson a little while ago and he suggested that repairing the disk permissions might fix the problem. I just did that and will be curious to see whether it does...

Well, we've finally upgraded to WV Arch 2010 (SP2), and the gapped line still has a short segment in the middle, contrary to Jeffrey's statement. Is there anything I can do to get rid of it? It shows up in a file I've imported from 2008, but if I create a new section cut in a 2010 file I've started from scratch the behaviour is exactly the same. Hmmm... Cheers, Markus

I searched the archives and found this thread describing the same problem that I've had for some time now, both under OSX 10.5 and 10.6 as well as under VW Arch 2008 & 2010. The keys work just fine under all other applications, but about one third to half of the time, when I boot up and start VW, VW doesn't seem to recognize the and keys for most if not all commands. A reboot usually fixes the problem. Certainly is annoying and time-consuming! Is anyone else (still) encountering the same issue? Cheers, Markus

Are you using ZCENTER in the database row? I still don't get a valid function in my worksheet using that, regardless of whether I set the document's units to feet, inches, or feet & inches...

oops, that was supposed to be 283.95' -- either way, it's definitely not in the three thousands... And I'm still wondering whether 2008 supports =ZCENTER ??? Cheers, Markus

I'm not sure how you got that result - the stake object elevations range from around 275' to 289'and the average that I calculated by hand was 298.95'. Were you able to extract Z values from the stake objects in the worksheet?

Thanks Jonathan, that's very kind of you. I thought about trying to use the stake object record format, but I didn't see a record field in that format that looked like it would contain the elevation. In any event, I'll attach a file with the DTM, stake objects, and the worksheet.

Yes, the report should be returning all of the stake objects on my site model layer, in the ABE (average building elevation) class -- see attached screen shots of the database criteria, the worksheet, and the OIP for one of the stake objects. Is ZCENTER definitely a supported function for VW 2008?