Jump to content

Pat Stanford

Moderator
  • Content Count

    5,090
  • Joined

  • Last visited

Everything posted by Pat Stanford

  1. Pat Stanford

    Symbols from 11.5 > 2008

    Based on the screen shot you sent, you don't even have to do a batch convert. You threw us all off track by talking about folders in Windows Explorer. You don't havea folder in Windows, you have a single VectorWorks file (AVW-Tele....) that contains a bunch of symbol folders. When you try to open this file in VW2008, it will automatically update everything in the file to the new 2008 standards. It will even ask you hwat to do about the name. You can either assign the old file the name with a VW11 appended to the end or append a 2008 to the new file. As to your comment about Photoshop and file formats, the change in file formats is what allows VW to grow. Without a modified file format, we would not have Section Viewports, Cavity Lines in viewports, 2way worksheets, and many other functions. VW2008 will just open the files and do the conversion automatically. When you use an old brush in CS3, is there any kind of conversion that is done? Can you take it right back out and use it in VER6? You can export back out of VW2008 if you need to get back to VW11, but you will loose the new functions. Pat
  2. Pat Stanford

    Symbols from 11.5 > 2008

    What you are actually saying is that you have over 100 individual VW files each with a single symbol in them. Petri and Christian are giving you good information that will serve you well in the future. My recommendation would be to bring all of the symbols into just a few library files before you convert to VW2008. In VW11, do an Add Favorites from the resource browser and select all of the 100+ files at the same time. Select each new "Favorite" in the Resource Browser one at a time and select Import. Save the file after each (or each few) imports. This file will now be your new library file. Add this new Library file to your Favorites in VW2008. In VW2008, you will have the option to export resrouces (symbols) to a library file, so after you convert to VW2008, you may never have to open that file again, just have it accessible to VW. Pat
  3. Pat Stanford

    Total parking space count

    Just use the Create Report command and use Record Parking Spaces is Present. If you want to limit it to just a single layer, go into the Database Header Row and Edit Criteria. Add a criteria of Layer is XXXXX. Pat
  4. Pat Stanford

    Shortcuts to Preference Tools

    Sent to soon. Here are some more prefs Zoom Line Thickness 9 Black and White Only 10 Adjust Flipped Text 13 Show Others while in groups 14 Black Background 16 Associate Dimensions 28 Pat
  5. Pat Stanford

    Shortcuts to Preference Tools

    If a double click is acceptable you can create a set a scripts (or download them from VectorDepot.com) that when double clicked will change the state of the pref to the opposite. The script is just one line. Copy and paste this into a blank Vectorscript (created from the resource browser.) SetPref(5,Not GetPref(5)); This will toggle the Snap to Loci. Depending on which pref you want to change, change the number (in both places) and save with a different name. It is probably easiest to duplicate from thr resource browser and rename there. All of the prference selectors can be found in the VectorScript Appendix (see the VectorScript documentation), but here are a few of the key ones. Offset Duplicates 1 Snap to Loci 5 Show Rulers 6 No Fill Behind Text
  6. Pat Stanford

    3d walls

    Walls, doors and windows are all inserted relative to the design layer z height. You can set the design layer z in the Organization Palette, Design Layer tab. Edit. It can be set separately for each design layer. This is very useful for multi-story work. Normally walls will insert starting at the layer zero point. Windows will insert with either a sill or header height relative to the layer zero point. This allows you to put in windows on the third floor without calculating the heigh above the file zero point. You have probably either gotten your walls moved up in the z above the layer zero point, or have your windows taller than your header height of the windows. Pat
  7. Pat Stanford

    Viewport names

    Petri, Have you checked the Drawing Label Tool? If you place a drawing label in the Annotations Group of a viewport, it will grab the name of the viewport as the DWG Title Field. It is not a live link, so if you change the name of the viewport, you will have to go through and change the Drawing Label also. It should be live, with an option to override. If you name your viewports correctly as you create them, at least it is a start. And you could easily write a script (wink, wink...) to go through an replace the text in the drawing label (or in a class, or with a record) with the viewport annotation they are in. Pat
  8. Pat Stanford

    Improved Dimension Text

    Perhaps we could get the long dash enabled as a kind of "unit mark". That would provide the visual separation, but not be interpereted as a mathamatical operator. Actually on second thought, that is a really bad idea. How confusing would it be to try to always use the right dash. If you entered 1?1/16" it would be right, but if you entered 1-1/16" you would get 15/16". I don't think the visual difference between the two is as great in most fonts as it appears in this post. Pat
  9. Pat Stanford

    creating Viewports in Design layer or in Sheet layer

    A viewport is just a set of Layers and Classes visibilities (Plus some other things) that act as an object. If you have the design layer set to look the way you want the viewport to look, and create the viewport from the Design Layer, all of those settings are included automatically. If you create the viewport directly on the sheet layer, then you have to manually set all of the settings. No matter where you create the viewport, you have all of the same controls over the content and apperance once it is created. Pat
  10. Pat Stanford

    Replace or clear out fonts

    Copyright is boilerplate (something that just gets added to every document). I should probably switch to Creative Commons and use a Share Alike for scripts I post here. Dimensions do not respond properly to the same code that works for other objects, so I check for them and handle them separately. I had gotten to the point of Dims not working and went searching my archives. Gerard Jonker had posted a script (via Matt Panzer) to the VectorScript List last week that supposedly does the same as mine, but must do much more because it is about 200 lines long. I noticed that he had pulled the dims out separately and this gave me the key I needed to make it work. Pat
  11. Pat Stanford

    door schedule worksheet re-ordering (numbers)

    In the Worksheet, there is a SUM icon at the top. Select the header row of the schedule and then drag the SUM icon to the column(s) that you want to sort by. You can edit the schedule as much as you want. Select a cell in the header row and you can see the formula for the cells in that column. CHange it as you need. To add addtional columns, click on the little black triangle at the top left of the worksheet. If you need to change the doors shown in the schedule (only doors on first floor for example), click and hold on the row header (e.g. 2) for the database and select the Edit Criteria option. Pat
  12. Pat Stanford

    raytrace issue?

    It was the critical thing. For a texture to show on an object, it must have a solid fill (any color). No fill, no texture. I am not sure exactly how or why you ended up with NURBS. I took a wide flange, ungrouped it and got a polyline. I then extruded it and went in to edit the profile. It was still a polyline. You must have converted the extrude to NURBS. I don't think that gets you any real benefit unless you need to texture different sides of the beam with different colors/textures. If you leave it as the extrude, you will have an easier time editing the profile and length if changes are necessary. Pat
  13. Pat Stanford

    raytrace issue?

    Double check your profile object. It is probably not a closed polygon/polyline. If it is a polygon, make sure the closed check box is checked. If it is a polyline, use the arrows in the OIP to step around each vertex. Look for the button that says Hide Next Edge to change to Show Next Edge. If so, click the button to show that edge. Repeat around the entire object. Then make sure that the object is assigned a fill in the Attributes Palette. Pat
  14. Pat Stanford

    Replace or clear out fonts

    David I think that what you suggest will only work if all of the layers are at the same scale. If you have multiple scales in the drawing, you would have to repeat for every different scale. You would also have to go in and do any viewport annotations separately. I think, that the script will handle all of the above challenges directly. Pat
  15. Pat Stanford

    Replace or clear out fonts

    How about this script. It will replace the font of every object with the current default system font. Thanks to a script by Gerard Jonker for a hint about handling the Dimensions separately. ========================= Procedure ChangeAllFonts; {Changes all of the fonts in a document to the current default font} {? 2007 Coviana, Inc.} {Vectortasks Training - www.vectortasks.com} {PodCAD Podcast - www.podcad.tv} Var H1:Handle; DefaultFont,TextLength,Kind:Integer; S1:String; Procedure ChangeFont(ThisObject:Handle); Begin Kind:=GetType(ThisObject); If Kind <>63 then Begin TextLength:=Len(GetText(ThisObject)); SetTextFont(ThisObject,0,TextLength,DefaultFont); End else Begin SetObjectVariableInteger(ThisObject,28,DefaultFont); ResetObject(ThisObject); End; End; Begin DefaultFont:=GetFontID(GetPrefString(100)); {Get the ID of the active font} ForEachObject(ChangeFont,(INSYMBOL & INOBJECT & INVIEWPORT & (ALL))); RedrawAll; End; Run(ChangeAllFonts); ===================== Pat
  16. Pat Stanford

    Musical Symbols

    They already did that at least once. Back in MiniCAD 4/5/6 (I don't remember exactly which one), the grand piano symbol shipped with the long side on the right. Pat
  17. Pat Stanford

    Tables and Chair PIO

    Petri, It might be worth trying to change the field type again. In VW12.5 the Space Object shipped with the Volume as a text object. It still seemed to work fine with it converted to a number. Perhaps the same would apply to the table/chairs. Pat
  18. Select the header row of the database. Drag the sum icon down to the column header. Repeat for the second column. Pat
  19. My 1 GHz G4 Powerbook takes about 40 seconds to load designer. Pat
  20. Try putting a sum icon in both the type and length columns. Add an additional column with a function of =count The other possibility would be to add an additional field to your record format that would specify exactly the type and lenght together and use that to do the summary. To set a record to be attached to every instance of a symbol, your first create the symbol then edit it. Deselect everything and then attach the record and set the "defaults" for that symbol. Exit the symbol. When you next place an instance of the symbol, it will have the record attached. Instances that have already been placed will not update. Thanks to Julian Carr for the background on this functionality. I stole this from a post he put on the VectorList back in 2006. Pat
  21. Pat Stanford

    Viewport names

    I agree. Not only the name, but all of the basic information about the selected object(s), [number of object, object type, name] should be available a the top of every pane. Panes are really a pain. Pat
  22. While the fact that bugs that effect your work are certainly frustrating, please take a step back and consider how much work goes into a release of VW. Have you never sent out a drawing, only to have someone point out an error that you missed? Or sent out a document with a typo on the first page? That is the kind of thing we are talking about. With the thousands of different hardware and software combinations that exist, it is impossible to test every option in every way on every system. Does NNA every choose to ship a product with known bugs? Yes, absolutely. Do they like to do so? I don't think so. They have a pretty good record of fixing the things they can, and the field length bug should be fixed soon. All of the people I know at NNA (dozens) are hard working and really care about what they do. But they are limited by the same kind of time and resource constraints that effect all of us. And it really does not help to make you case and get you bug fixed sooner by being nasty and claiming that they have done this on purpose. Pat
  23. Pat Stanford

    worksheet not show volume "cu ft"

    After taking a look at the file, I can unequivicably state that we are both right!!! VW does correctly put the Volume units in when formated to do so and the column contains a number. Your formula of =(space.volume) is the correct one to get the data you want. The problem is that there is a bug in the Space Object!!! The Volume parameter is formatted as Text rather than a Number. This means that you are getting a column of text where you think there should be a number and the volume units are not showing. Two possible work arounds: 1. Go into Tools:Scripts:Plug-In Editor. Select the Space plug-in. Click the Parameters button. Scroll down to and hihglight the row that says Volume. Click Edit. Change the Type from Text to Number. Click OK. 2. Put in a different formula. Instead of using space.volume use (Space.Area)*(Space.'Extrusion Height') This has a minor difference from the space. volume, probably due to rounding errors, but it does not seem like much. Pros and cons: 1. Pros: Fixes the problem. Seems to be stable. Cons:Fix will have to be repeated every time the Space plug-in is updated. If you are already on 12.5.2, there will probably not be more updates and this should not be a problem. 2. Pros: Must remember and use the more complicated formula every time. Cons: Slight Rounding Error. In either case, the Space object has been substantially reworked in VW2008, so this does not appear (tested) to be a problem there. space.volume shows the unit marks OK in 2008. Pat
  24. Pat Stanford

    worksheet not show volume "cu ft"

    Take another look at your volume formula. The number in the database header is 29 Cu. Ft. I bet you have 29 rows in you database. The number in the database header is normally either a count of the number of items in the column if the items are not numbers, or the sum of the column if they are numbers. The "value" in row 2.1 is 328.7. This is way more than the "sum" of 29 that I would expect. I think your formula is somehow returning a string rather than a number. The worksheet can then not apply the formatting to it becasue it is not a "number". Pat
  25. Pat Stanford

    worksheet not show volume "cu ft"

    I can't duplicate your problem here on a PPC OS 10.4.10 Designer w/ RW 12.5.2. Check that the formula you are using is truly generating a number rather than text of digits. The column header of 29 looks like the number of items, not the total which it would give if you had numbers in the column. Pat

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×