Jump to content

Search the Community

Showing results for tags 'annotations'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design
    • Terms of Service and Community Guidelines

Calendars

  • Community Calendar

Categories

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

Categories

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

Location


Skype

Found 4 results

  1. I may have heard from a little birdie that a broad overhaul of labeling capabilities/tools may be in the works in coming versions. As I have become recently aware, the solution may already be hidden in the irrigation tool suite and it might not need much tweaking to become the full scale labeling tool we need. The Tag/Label Tool within the irrigation tool suite not only has the ability to label irrigation objects with inherent data in a variety of customizable label styles; thanks to @Bryan G. I just learned that the tool can actually represent ANY data attached to objects in plug-in parameters or custom record fields. This is HUGE. In order for this tool to become the tool we need however, there are still a couple of tweaks that would inform an ideal workflow. The Tag/Label, when placed on an object, needs to lock relative to that object. This means that if the tagged object moves, the tag/label moves relative to it. Note that not all labels need to point directly to the object, but in the general direction and this functionality needs to still exist, but in this case, if the tagged object moves, so too should the tag/label move. Ability to save styles and remember most current - When tagging/labeling different objects the style or data labelled might change. There needs to be a way to store these different styles and the ability to choose from them, but also remember the last one used so that it doesn't revert to a default setting each time a label is placed. Act Like Keynotes Placed as Keynote Callouts - Auto-numbering and organization are the primary benefits of using keynote callouts currently and we use them almost excessively considering the difficulties with managing the callout database. This tool has the potential to offer the benefits of that tool without the fuss. If the tag/label chosen has the ability to be represented by a Keynote Callout that puts the label in a Keynote Legend and auto-numbers/letters similar to callouts currently, we could then build extensive keynote legends/worksheets based on objects' inherent data that auto-numbers. Place in Annotations - I imagine that this is perhaps the hardest ask, but it is potentially the most influential...we need the ability to somehow use these Tags/Labels in the Viewport Annotations space while still linking to the objects present in the design layer. It is far easier to organize labels for legibility when placed in the annotations and it removes design layer clutter. Additionally, when placing callouts in Viewport Annotations you can take advantage of the viewports margins and white space to aid in legibility and organization. This isn't something you can do when placing on design layers. Finally rotation...many viewports are rotated and in order to represent labels on these viewports when placing in design layers, you must rotate them to read horizontally...often in very extreme angles which just adds to the clutter, confusion, and chance for error. All in all, this tool is very close to what we need and I am excited to find ways of working it into our workflow. My hope is that VW takes this into consideration when working on any new Tag/Label tool.
  2. Is there a way to control the appearance of auto generated Annotations on a per file base in a centralized way, without the need to go into Annotation Layer for each Viewport ? For example the Viewport Titles appear in the bottom middle only. When I move them and change Crop Geometry they don't follow. Is there a way to define them globally with XY distances from a fixed origin like bottom left or bottom right ? Or a centralized file setting to define a global Font to a document ? I created Text Styles but every time when I create new Viewports, things start "undefined" and for later edits I can only change 1 Viewports Annotations at one time (?) Did I miss something or doing it wrong ? Are there already kind of "Section Line Styles" or global Headline, Sub Headline, Standard, ... Text setting like you would do for a HTML web page by CSS ?
  3. It would be nice to have some indication that there are objects in the annotations level of a viewport. Maybe this is shown as an icon that can be switched on an off directly on the viewport, or some notice in OIP. Or maybe a dialogue box that alerts you to the objects after you try to delete the viewport if you forget.
  4. Hi I have a structural model, and I've done section viewports in a plan view, to be rendered as hidden line. I have 3d conversion set to low for speed, and they have a depth set (not infinate) I render the section, and it looks lovely... when I go to annotate it, on entering the viewport it displays as hidden line, with tonnes of unnecesary extra lines making redraw very slow and difficult to annotate. When you exit, you need to update the viewprt and then it displays as expected. Previous versions of VW always allowed you to annotate the hidden line render, and not go to wireframe.... anyone else with this issue? PC, Win 8.1, Nvidia graphics Cheers

 

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