Jump to content

Search the Community

Showing results for tags 'graphic legend'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
    • Forum Feedback
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Energos
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
    • Data Tags
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design


  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs


  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me






Found 7 results

  1. HI I'm struggling with defining the Graphic Legend Field - (no coding knowledge) If Mark is empty on the Wall Style Data Tab, then the Legend reads the 'Name' #AnyIFCEntity#.#Pset_WallCommon#.#Reference# (default from Vectroworks original setup) If there is an entry in Mark, then it reads the Mark . How to define the 'Mark' and the 'Name' from the Wall Style Data tab? Thanks Tali (apologies - I may have posted this on a PM before) Wall Graphic Legend Trial.pdf
  2. As above, this would be a really useful functionality that would allow symbols or styles to be clearly identified on a drawing with an associated Graphic Legend reporting that data about that object/style. For us, we could then basically automate the way in which we identify differing wall styles on drawings. Currently this is just a regular viewport with all the colours added to the annotation space. The wall descriptions are then manually typed out. This introduces a lot of potential for errors, not to mention it being a tedious task. Other people have different uses for it as described here. This could be an extension of the "Filter by Viewport" option of graphic legends or something else, but certainly it seems like the functionality to achieve this is present in VW albeit in separate parts.
  3. Got my graphic legend working for doing fixture summaries, and that works great, pulls in Type, dmx channel count, weight etc. is there any way for the graphic of the fixture to render with the color of my data visulization? I usually color code fixtures on plots and would love for the key on the side to match. Currently just renders in the default texture it looks like. pic attached for example.
  4. Hello, Is it possible for graphic legend based on material name to include information like material description, mark, keynote ... We have tried with worksheet function: #WS_MATERIALPROPERTY('MaterialKeynote')# but it is not working. Is there a way to extract these type of data? Any suggestions much apreciated.
  5. I am trying to create a graphic legend, using a few simple 2D symbols, to which very simple 2-field Record Formats have been applied. When I go to edit the Cell Layout for the Graphic Legend and create a "dynamic text" item, when I select the symbol's Record Type & Field and try to create a dynamic text component as part of the Graphic Legend cell layout, the Graphic Legend appears to simply ignore the item entirely. It doesn't show up at all in the layout, even as an empty place-holder. When I change the data source for the dynamic text item to be an Object Function (such as "Area"), then everything works fine. Is this a bug, or am I doing something wrong? Note that the Cell Layout is identical in both examples. Here's the PROPERLY WORKING example: And here is the NON-WORKING example:
  6. Hi everyone, I am using the new graphic legend tool for a booklet representing prefab facade elements of a building. Any prefab element is a symbol (hybrid 3d/2d) with an attached record. Within the graphic legend cell, I would like to insert a text (dynamic text of a graphic legend field) showing the overall amount (=count function) of each prefab element (=symbols). It seems to me it is not possible to call the "count" function via dynamic text definition. Any idea/suggestion on how to do that? (e.g. showing how many times the item shown in a graphic legend cell - in window reports / wall type reports / symbol reports / etc.- is used in the drawing/file and/or within the selected criteria).
  7. Recently ran into a problem in graphic legend referencing. In abstract, I believe the graphic legend tool has the ability to potentially eliminate drawing wall type details by about 50% if not more! Currently I am trying to use the Graphic legend tool to essentially do just that - create details for all the wall types, floor types, symbol types etc...to be used for current and future project in our office. I have succeeded in the most import aspects - extracting component and material information from these elements. There are just a few things missing - a scaling reference (one shown in GRAPHICLEGEND scale) and a number sequence for image cell numbers. It seems they already autopopulate the numbers given that each image can be previewed seperately as image cells (see below). These number can then be used as detail callout numbers from the plan (not necessarily referenced, but indicated / recorded). I think this would be a huge timesaver for many people here. DATATAG COMPONENT CALLOUTS.vwx My wish is to be able to extract this information into the dynamic text properties (i.e. #WS_Objectdata(GraphicLegend#, scale) or something similar, and #WS_Objectdata(Graphiclegend,cell number) or something similar. But here is the prefinal result! I'm attaching my reference file to show the remaining information that can be extracted from PIO's.
  • Create New...