Jump to content

Search the Community

Showing results for tags 'callouts'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • 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

Categories

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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 7 results

  1. I'm trying to help a user with these issues. I'm making this post to gather more information to either inform my bug report or provide an informed solution to the user. Primarily, I would like to establish if anyone else has experienced the following symptoms/issues when using Callout Notes and Keynote Legends, with a Notes Database. Issue 1: Notes previously in the database no longer being there. (As evidenced by inspecting a copy of the backed database file). Issue 2: Keynotes and their respective listing in a Keynote Legend disappearing. From what I understand, these issues occurred under the following conditions: New Vectorworks document created from template. Previous Notes Database file duplicated for use with this project only. (Database is stored on a local network server, but the Vectorworks file is on the computer being used). Callout Tool Preferences used to select the duplicated database file. Notes placed as Keynotes, on Sheet Layers in Viewport annotations. (Notes Manager 'Prefs...' set to save changes when dialogue is closed, 'OK') Keynote Legend/s created on Sheet Layers (not in Viewport annotations). File saved, then closed. File later reopened. Some Keynotes and the respective items in the Keynotes Legend are missing, but other instances of these Keynotes are still present on one other Sheet Layer and listed in the Keynote Legend on that Sheet Layer. The Keynotes that disappeared were not present in the original database before it was duplicated for use with this project. They were created during this project. When using 'Reconcile Notes' the following error comes up for some notes: "Cannot find the selected note in the Database". - All the notes in this instance start with the same prefix / naming convention, 'GF-PF' and are found in varying quantities in Keynote Legends on several Sheet Layers. I see potential for this discussion to start a torrent of contribution, so please note I am not the user so getting more info from them or testing every remedy offered might be limited. The conditions supplied above are intended to inform what variables might be involved for others with these issues to consider, and to help inform the scope of these issues. The most important factor for me is to establish if anyone else has experienced the following symptoms/issues. Thanks! Jeremy
  2. REdmondson

    Meeting Planning

    The company I work for is in need of a callout that links to database sort of how vectorworks and lightwright speak to each other. I want it still to have the functions of a callout but the text needs to be editable on both sides of the database and VWX. Does anyone have any ideas?
  3. Itchy

    Reshape tool on Callouts

    The reshape tool used to be able to be used on call outs but it now seems to have no impact. Bug or no longer a method to use?
  4. I spend WAY too much time arranging callouts on my drawings... I wish that callouts could be arranged by their text bodies (as if they didn't have leader lines) using the "Align/Distribute Objects" command. And I wish that their leader lines could then be adjusted without affecting the text itself (i.e., I wish moving the "shoulder point" didn't also drag the "label point" along with it). Maybe the "Align/Distribute Leader Lines" tool is useful for creating "Parallel objective liens," but otherwise it doesn't really seem all that useful: 1.) it's methodology is inconsistent with and contrary to the simplicity of the "Align/Distribute Objects" command; 2.) it distributes callouts vertically by their shoulder lines, with no option for equal spacing between callouts with differing numbers of rows of text; 3.) and it distributes callouts vertically based on the vertical distance between the top two callouts, rather than distributing them between the top and bottom callouts. VWIS018
  5. Noticed an issue with the callout tool. I've placed a callout in a design layer. When it's in a viewport on a sheet layer, it's fine. However, if I used the viewport advanced properties to scale the text, the callouts scale and move. I won't argue if this is a bug, a feature, or it's supposed to work this way. Callout Issue.vwx
  6. Good afternoon everyone, I've been working on a set where i have alot of callouts for plans, elevations and sections that seem to be repetitive but not parametric, and i've been wondering... Is there a way to combine notes database with a callout tool or perhaps a bubble revision tool? I've been thinking of a simpler way of marking up notes by using annotation bubble revision markers and linking them to notes that are shown separately on the sheet in list form. There are multiple reasons why this is a useful feature 1. CSI can be embedded into notes parametrically - unifying elements in the project to specifications without any deviation to notation 2. Simply the callout process in plans - and eliminate clutter by referencing notes beside the plans. 3. No errors in documentation 4. Information is centralized - and modification to notes or finishes can be made remotely. 5. Notation tool does not need to be updated independently from the bubble revision callouts - they're intended to work simultaneously. Method - My current method is simple - i created a 2 custom record fields one for number, the other for description of the object - and reference those records in a table for that layer only. I however - end up having to make one table for each layer (floor plans, rcp, tenant protection plans, fire safety plans, etc...) which is the only nuisance. I end up having 10 - 20 worksheets just for that set. Is there a way to combine this method with the notation tool? and is there a way to eliminate duplicates? perhaps a method that would allow us to use one worksheet dynamically? Either way, I know this feature doesn't exist, but i figure , if anyone has any ideas how to combine these tools, i'm all ears? perhaps Nemetchek will hear us? Thanks everyone!
  7. Dragged copies of Callouts lose their Text Style and become <unstyled> . I have also submitted a VSS Support Request for this. STEPS: 1. Create a Callout with a Text Style. 2. Click-drag a copy of that Callout; 3. Either drag the Callout leader so that the Callout flips sides, or double-click on the Callout to edit the callout text. 4. Upon finishing editing the text of the Callout (or making it flip sides) the Callout will lose its assigned Text Style and become <unstyled>. I sure hope the new Vw2017 Analytics reporting feature can see how much time I spend on stuff like this.

 

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.

×