Jump to content

Boh

Member
  • Content count

    177
  • Joined

  • Last visited

Community Reputation

18 Good

About Boh

  • Rank
    Journeyman

Personal Information

  • Location
    New Zealand
  1. Reports Records Database Worksheet Schedule

    Ooooo! Some way of comparing rw styles, texture effects, viewport settings would be amazing!! I find that aspect of VW a bit of a struggle, as I'm sure others do. Trial and error practice of setting up 3D viewports is very time expensive, especially when you have to wait for a viewport to render every time you tweak a setting. ill be closely following your blog! Extending worksheet functionality to report not only on objects in the drawing but also resources in the resource manager (not actually as part of an object in the drawing) would be very useful. Worksheets could then be developed to report on textures, hatches, images, all resource styles (including render works styles, wall styles, text styles etc etc.) and more, so that you could use the reports to compare and select the resource you want use. Re my "brief" post above: I'm a relative novice at worksheet practice. The little I know has been gleaned from gurus such as @michaelk , @Jonathan Pickup and @Pat Stanford. In fact in response to your post I first tried to find one of pat's posts I recall reading that had pretty much the same explanation ( but better) but I couldn't find it so just wrote my own! Edit: aha! He's just posted it!
  2. Reports Records Database Worksheet Schedule

    I feel your pain Grethe! I had the same probs understanding this stuff when I first started getting into it. In brief: Essentially worksheets and records are tools that can be used to produce reports about objects in your drawings. You can attach information to objects in your drawing through the use of records. For example you may have a symbol in your drawing that represents a light fitting. Using records you can attach information about the light. The record could be made up of one or more different "record fields" with each field used to enter different info about the light such as its make, model, output, price etc. You can create and customise records and attach them to almost any object. You can attach records to objects as well as enter field info about the object via the data tab of the OIP. You can create records or edit extg records via the resource manager or alternatively via the tools>records menu. Objects with the same record attached do not have to have the same info entered into their respective record fields. E.g. One instance of your light fitting symbol with the "light fitting" record attached may have a record field called "power" that has 50 watts entered and another field called "price" that says $200. Another instance of a light symbol with the same "light fitting" record attached, may have 35 watts and $75 entered into it's "power" and "price" fields. So you may be asking what does all that really mean... This is where worksheets come in. You may have a reflected ceiling plan with lots of different light fittings. All the light fittings are represented by symbols which have the "light fitting" record attached. Using worksheets you can create a report of all the light fittings in the drawing. You tell the worksheet what criteria to look for, in this case the "light fitting" record. A report is produced in the form of a table contains data base info on all the objects in the drawing with the " light fitting "record attached to them. Each row of the table represents a different light fitting and the various columns each represent the info entered into the different record fields. As well as record info you can also include other info about the objects in the table such its class or layer, it's scale, the symbol name etc. Similarly to excel you can enter functions and make calculations on the data in the report. E.g. You could sum the "price" fields or just simply count the number of fittings. One of the cool things about reports is that they work two ways on record fields. I.e. You can edit the record data attached to objects in your drawing simply by editing it directly in the worksheet rather than from the object itself. Once you have generated a report you can edit and format it the way you want, sum or summarise different columns, add a title and if desired place it as a Schedule on your drawing. In our light fittings example we could place the report we generated as a "Schedule of Lights". This is just one example. You can create records and reports on almost anything - not just symbols. Window and door schedules are another common example which call up record info attached to door or window ( or WinDoor ) plug in objects. Drawing lists too are a simple example of a schedule that uses the title block record info as the reporting criteria. There is a whole bunch of functionality about using worksheets that is too much to detail here. I hope this helps. I'm sorry I didn't put any graphics in to help illustrate as not in the office atm. Can poss send some examples tmrw.
  3. Yes however if you are spending a good amount of time creating classes then I would recommend building up s set of standard classes that you use and developing project templates which already have these classes in them. If you don't always need every class for every project then you can create a "myclasses' file that is kept in the VW user folder Called "standards'. When you want a new class you can then right click on the classes tab of the Nav palette >New class>import and your "my classes" file will appear in a drop down list among a bunch of other default VW standard files. Select your file, choose one or more classes that you want Done. If you find yourself often creating the same classes on different projects then this is definitely the way to go. Added benefits are: The class attributes can be set up exactly how you want them. I.e . No further editing is needed the classes can confirm to your class-sub class naming system to seamlessly be incorporated into your project files Standardised classes can be integrated into your symbol library, wall, roof, slab styles etc
  4. You have dual monitors? If you make the whole VW window floating then stretch it out across the two screens you can then have floating Windows of different files inside the main VW window. Pretty much like in your image.
  5. model origin in section viewport

    i don't think there is an origin point as such in section and elevation viewports. im interested to know why you want to know that? If you use the benchmark tool with "Y value relative to reference elevation" you can at least work out the z=0 height. But it looks like you have figured that out.
  6. Open Recent Menu Popouts

    I'm It would also be great to have a right click "open location" option on the open recent tab so that you can find where you mistakenly saved a drawing...
  7. Parking spaces

    Anyone else find parking spaces a bit buggy? After a time the stop being editable. I.e the vanish whenever you try to edit them. I need to restart VW to get them working again. Happened it 2016 too
  8. model origin in section viewport

    What about placing a locus on the user origin of a design layer and cutting and pasting it in place in a section viewport annotation? in theory it should past at the origin point of the section view. There is also a setting on the elevation benchmark tool that will reference the z height on the section (can't remember what it is called exactly).
  9. Clip cube perspective viewport

    This is a great video tip! In in the past I have also taken screen shots and pasted the image onto a sheet layer. Can this technique be used for a iclip cube view that clips 2 or more parts of your model? E.g.a view of an internal staiR
  10. vectorworks help bug

    '=' also happens to be the default mirror key. (Or at least used to be!)
  11. Yes please! Especially frustrating when you want to remove a field but first have to remove a choice that is by record field. When rebuilding the choices again there can be so many record fields to scroll through to find the right one again.
  12. There is a toggle for a perspective crop if that is any help?
  13. Hi Grethe. Not sure VW help will er..help!... Here are a couple of screenshots that might explain better. Whilst working in a design layer it is sometimes good to know where the edges of the viewport crop are so that you can make sure all your notes can be seen in the VP and not cut off. I'm all good now thanks with the SP3 update. It has finally arrived in New Zealand :-) !!
  14. One use is use so that when you are adding notes on a design layer you can keep the notes within the extents of the sheet layer vp crop. I do however put them on a "NonPlot" class as soon as I create them so I can turn them off in my viewports. Once I do that I uncheck the check box in the edit vp dialogue so that I don't make any more rectangles unnecessarily.

 

    • 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.
×