mr. iagea

I heartily third the motion!

The application of arrowheads is rather kludgy. It takes a double action to apply arrowheads, and these two combined actions are not adequately explained in the documentation. Currently, to apply an arrowhead, one must select the type of arrowhead from a menu in the attributes palette, and then ALSO click a button to engage (enact? apply? encourage?) the arrowhead. This is counter intuitive. A better solution (IMHO) is to have a single function, that being a menu from which you select the type of arrowhead desired. This menu would include a "None" option, thereby making the need to have a "switch" (which is really all that little arrow button is) to turn on or off arrows. Furthermore, this would go far to remove the confusing arrowhead option when creating classes. Without knowing how arrowheads work, one assumes that ALL classes have arrowheads (because they appear to be active as an attribute in the class attribute creation dialog. In my solution, if the menu item of "None" is selected, then the small pop-out menus (that currently show an arrowhead, when there isn't one active) would have an "X" or something showing, so as to be visually certain that no arrowheads will be applied to the class.

It would be a good improvement to be able to update referenced viewports in the same way that other viewports are updated, by a button in the OIP, as well as include it in the "Update all viewports" command (otherwise, the command should be renamed "Update Some Viewports").

Perfect. Thank, Pat! This is an example of some of the inconsistencies I find in VW. I see no reason not to have the update functionality in the OIP, using the same button that one uses to update other viewports. of course, leave it in the references tab, too. Just make updating easier, as that's a common function. cheers!

I bought that book when I first got into VW, but I ended up returning it because it didn't answer the questions that I had. The training method used in that book takes a sample project and goes through the process of creating it in VW step by step. Of course, the info and the presentation are subjective, so it may help you and it may not. That totally depends on your intended use of VW and your current overall software application competence level. Personally, I had the training DVD's that came directly from NNA, and I found those to be more educational than that book. If you have the Training CD's then that book duplicates the info (more or less). If not, then the book might be a less expensive option than the DVD's, which are available directly from NNA (check their website). I also encourage you to investigate the free training resources which are posted on NNA's website. Training Guides http://www.nemetschek.net/training/free_resource.php Training Videos http://www.nemetschek.net/library/index.php I believe there is a link there for some tutorial books which are priced similarly to the one you've located on Amazon. The learning curve with VW is fairly steep, even if you have previous experience with vector-based and/or CAD-like drawing apps. It's steep not only because it's a complex application that is attempting to do many things. but also because, as with all software, there are idiosyncrasies and inconsistencies with both itself and common practice GUI functions in other software that make understanding how VW works a real challenge. This forum is a great source of helpful info, with many seasoned VW users that are happy to provide help. I encourage you to make use of this valuable resource. HTH

OK, here we go... I have a file into which I've drawn all my standard construction details. I have them grouped in that file the way I usually have them on my plan sets. I want to simply create a viewport in my working file of each design Layer (in the details file), so that I'm simplifying my work (ha!). Creating the viewport in my working file went fine, but then I had to make a small edit. I double clicked the viewport to go to the referenced file and made the change. All good. But, now my working file VP is displaying the old info and there is no button in the OIP to update it. When I select "Update all viewports", nothing happens. When I go back to the details file, I get a message telling me the file will look different because the viewport is out of date (wow, ya think?). I dunno, maybe something more useful than that would be a better option for a message here (maybe like, "Would you like to update the viewport?"). Further, I cannot seem to just wipe clean and start over. I cannot erase the reference from the Create Viewport > Source dialog. How do I update a viewport from a referenced file? How do I delete the reference entirely? Thanks.

Cool. Thanks, David! Turns out I did have a "Ceiling-main" class. Turning that off removed the wall lines across the doorways. I don't recall creating that class, so I am assuming it's an auto-created class. But now I'm curious which function created it. I shall sleuth on! Thanks again!

Is there a keyboard shortcut to prevent a symbol object from being placed "In-Wall"? For example, if I set a sink symbol, and I'd like it not to snap to an In-Wall position, I'd like to control that more easily when I set it. Corollary: there seems to be some different editing for In-Wall objects vs Not-In-Wall. Can anyone tell me why that is? What's the usefulness of that? Thanks!

If you are working on a Mac, be sure that your system keyboard settings are not interfering. Go to System Prefs > Keyboard & Mouse, then click the "Keyboard Shortcuts" tab. There, you'll see many options for setting keyboard shortcuts that can interfere with an application's settings. This is not always the case, but I always have the absolute minimum system-wide keys set in my system prefs to avoid potential conflicts. HTH

Thanks, that fixed it. Ok, is it me, or is this highly stupid? How do I submit this as a bug, because if this is a "feature", some engineer at NNA needs to have his head examined. And while we're on this topic, I'm going to do everything in my power this morning not to rant about yet another ostensibly idiotic GUI thing. But seriously, the arrowheads, er I mean, markers. Okay, never mind... It makes no sense to have to click a teeny arrowhead to tell the program that you're going to have an arrowhead, but then to APPLY the arrowhead, you have to select the arrowhead you want from a totally separate menu. Even if that menu is right next to the APPLY "button" (I use that term so loosely, it fits like a bedsheet on a flea). A more sensible approach to this function is to have the arrowhead type menu be the only application method, and include a "None" option. Right? You either have the arrowhead or you don't. There is no third option. Unless of course you're an NNA engineer, in which case you have a special fourth dimensional third option where you have the arrowhead, but not really until you spend three hours finding out the super secret second half of the puzzle to apply the arrowhead. Something Yours Truly suffered before discovering the NNA Arrowhead Application Special Sauce. Not unlike the Worksheet Column Sort Chiclet Moving Thing). This lack of a "None" arrowhead option becomes more of an Achilles heel when one is setting up a class and the line should be devoid of arrowheads. To the unwashed, it seems that a new class's line options have, by default, arrowheads and with no way to remove them. It is totally unclear that those arrowheads won't be applied unless one clicks the annoying small arrow symbol in an annoyingly small attributes palette. Yes, yes, I get the whole global attributes thing. But is that really a good idea? How many of us have stumbled upon that, forgetting to change the class, not realizing the arrowhead is selected until one of your doors has every line with an arrowhead on it (yeah, THAT made sense!). Global attributes are what classes are meant for. IMHO, NNA has much to learn about GUI, and could learn a great deal about elegant design from the erstwhile Macromedia's FreeHand vector drawing application, specifically versions 10-MX, wherein ALL editable attributes for ANY selected object were available from an Object Inspector Palette (a term I also use loosely to describe the incredible fickle OIP in VW). To sum up: Arrowheads, nee markers, should be applied with a SINGLE function, that being a menu that selects the type of arrowhead desired, with an option of "None". The Stroke/Fill/arrowheads functionality could (should?) be duplicated into the OIP, as these are functions that are applicable to a selected object. Again, much to learn from FreeHand here. Just my fun little rant, albeit spawned from an unfun little foray into NNA wasting my time with some highly stupid arrowheads all over one of my doors. GRR. I guess it's my own fault: I PAID for this torture. ;-D

Okay, so I open my document, no changes. I notice that one of my doors looks like this (see attached image). Any idea what might have caused this? I even cut this offender out, and replaced it with a known good exact copy of the same door from a previous file, and it STILL came in looking like this. What's up?

I have a related question. How does one go about formatting the text (font face, size, etc.). As per usual, VW doesn't seem to do this in a consistent manner (i.e.: select the worksheet (once placed on the drawing), then select the text and finally select the desired formatting.). eh? EDITED: Never mind...I found it...yes, in a place I didn't expect it to be (drat that naturally intuitive mind of mine!).

I was able to get some additional help from the "Spread Sheet Reports" thread. I finally got it to work and found the hidden classes. Thanks a lot!

Yes, I had considered that the object may be embedded. Your suggestion is a good start. I'll try it. Thanks Pat!

I would concur with what everyone else is saying. Do the free upgrades now and determine if you are still running smoothly. If you're doing just basic 2D work, you may want to wait to upgrade until you have the cashstack to get a new machine. 2008 ran fine on my G4 iBook (1.87GHz/2GB RAM), but the tasty GL renders were a bit slow. It was my intro to VW, and I soon upgraded to a 24" Intel iMac and everything was great. I'm now running 2009 w/Renderworks with no noticeable delays. I do mostly standard B/W building plans, but I have been using Renderworks on this current project and my machine is still running just great. No delays, but then I also haven't put in multiple light sources and a bazillion textures, either. Most PB G4's were capable of up to 2GB RAM. It depends upon your machine. Specs can be found here: http://www.everymac.com/systems/apple/powerbook_g4/faq/powerbook-g4-how-to-install-memory-ram-types-supported.html HTH, charlie

Does anyone know of a way to find out which objects have which class? I'm tying to remove some unused classes, and one or two come up with the error about re-defining objects. Problem is, I can't see which objects have the attribute applied. I've tried turning off the visibility of all the other classes in an attempt to see what was remaining on the document, but nothing showed up. Is there a tool similar to "Purge unused objects" that allows you to see which classes are actually assigned to objects and then which objects? That might seem like a lot, but both Illustrator and Freehand have this ability. Eh? Thanks!

Cool. That makes a lot of sense. I have no trouble deleting annotations?it's nice to know what the VP's function is. Now I don't have to make a new VP every time I want another version of the same view. Thanks for the clear explanation of the VP. As always, great help, Pat. Best to you for the new year.

Great! I guess I would have tried that but I was under the impression that VP's were discrete objects for each use. So, if I copy a VP that now has dimensional info in the annotation, I'd have to delete all that and then the copy is a unique object?

Maybe I'm missing this, but is there a simple way to align VP's across sheet layers? In Design layers it's easy to turn on several layers and have some present greyed, so that different floors or objects can be aligned atop each other correctly. I'm looking for a functionality similar to this for Sheet Layers. As it is now, when I want to place several floor plan viewports (one for floor plan, another for electrical, for example) on their respective sheets, and have them aligned in the same location on each sheet, I have to toggle back and forth between sheet layers and move the VP manually, which is a tedious and inexact process. Any ideas? Thanks in advance! Happy New Year! charlie

David, Open "Vectorwork Help..." from the Help menu within Vectorworks to launch the installed online help system. Once there, click on the "Search" tab, then enter this exact text: "Creating a Custom Title Block in the Design Series" (just "title block" will also suffice). You should then be presented with several help entries that explain how to build a custom title block, including how issue data fields are entered and function. Specifically: #87 (Fundamentals), Creating a Custom Title Block; and #100 (Design), Creating a Custom Title Block in the Design Series. The latter explains the issue data fields. Be sure to place them directly in your title block symbol, not in the title block record. hth

Yes, that's what I've ended up doing. I used one of the ungrouped handles as a starter and then duplicated that, in its own class. Works great (for a workaround! ;-) ). Thanks for your help, Peter. It's greatly appreciated.

Okay, phew! Thanks, Peter. Yes, stuff like this is getting to be the norm (insert "grr" here). It's strangely relieving to see it's happening on your machine, too. I tried the ungrouping thing, too, and was astonished at the layers of groups. Thanks for checking that out. Murphy's Law of software design got me again! So, umm, any idea how to actually remove the handles? There doesn't seem to be a "None" option in the handles section of the OIP. My clients don't have trolls living under the house to manage all those handles...

So (sigh), another thing I've tried the first time that doesnt work as described. Frustration! Okay, I've pulled in some kitchen cabinet symbols, set them all up nicely and then decided to add some handles (so the interior elevations look better). So, I select a placed cabinet symbol, scroll down in the OIP to the buttons for drawer and door handles, select my desired handle and it shows up on the cabinet. Great! But only for a moment... Now, when I put handles on another cabinet, going through the exact same process, the handles do NOT show up on the second cabinet. AND, the handles I made on the first cabinet also disappear. So I go back to the first cabinet to re-place the handles (following the same procedure again). No luck. No handles. And from then on I cannot place handles on ANYTHING. They ALL disappear. Ideas? Thanks! UPDATE: Okay, so I tried this in a separate, new blank file. When I place the cabinet the first time, handles show up okay, but when I changed the handle type to another handle, they disappeared. So, I changed them back again, the handles did not reappear. Zooming out, I noticed the handles now about three feet (scale considered) UNDER and IN FRONT OF the cabinets. Then, when I went to move the cabinet, the handles ended up a few feet BEHIND the cabinet (and still a part of the symbol). See the attached image file so you see what's happening on my screen. The small one with the two cabinets is the test file. Th larger one is my atual file, with wall classes off so I could find the handles. See them there, about 12' below and to the left of the kitchen? Yeah, man. That EXACTLY where I want my kitchen cabinet handles, NNA. I've also attached the actual file, if anyone wants to see if that's happening on their machine. Thanks a lot!

That actually didn't work. I don't have time anymore to devote to this bit but I will try it later with a new title block. The solution that you gave before seems to be working, so I'll stick with that for this particular set of drawings. Thanks a lot for your help!

I tried this, adding "S_Drawing Number" to my title block record, and the drawing label does indeed take up the info placed in that field when editing the sheet's title block data. Solves the problem, however it seems as though since there's already a S_SheetNum field, that the drawing label should take up that info, as that's the info that actually needs to be in the lower section of the drawing border. Ah well, this solution works. Thanks, Pat! Just yet one more little thing to keep in mind, I guess...I yearn for consistency!