Jump to content

Search the Community

Showing results for tags 'styles'.



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

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 6 results

  1. It would be incredible if Hardscapes and Landscape Areas could be managed by Styles, similar to walls, roofs, slabs, titleblocks, etc. With this functionality, these would be saved as resources similar to Wall Styles, Roof Styles, Slab Styles, etc. and then could be edited in one location to make changes throughout the document. Currently the functionality of Save Hardscape... or Save Landscape Area... does create a resource manager resource, but that has no effect/connection to the instances located in the drawing. Furthermore, it really can't even be edited in the resource manager. Right now, the only way to enact large changes to multiple similar hardscapes is to make the changes to one and then use the match properties to apply it to all others. There are several reasons why this isn't ideal, Very Slow - Matching properties to hundreds of hardscapes or landscape areas can take forever to complete Inaccurate - The match properties workflow is a manual selection workflow and is only as precise as the users selection abilities/criteria It's time to rethink the way the Landmark tools fit within the greater movements of VW tools, I feel like they are out in their own little world and really should be brought into the fold.
  2. zoomer

    Window Styles Strangeness

    Window Styles behave strange for me in VW 2018 SP0-1 1. Changing Styles Windows in Walls do not update reliably. Sometimes I need to pull them out of the Wall and back in. (Not 100% sure on this, could maybe be a editable Style Setting Component, but for sure I had cases where pulling out/in updated my Window) 2. Duplicating Styles May destroy/corrupt their Preview generation in Style Settings dialog. And therefore RM thumbnail and preview too. 3. a) Corner/Non Corner Windows Window Mode : Fixed Glass (Jamb+Sash+Glass) I use a Sash Depth Offset. As soon as some Windows, using that Style, are set to Corner Mode, this Offset will be ignored, sometimes even set to 0,00 in Style. All Windows will lose Sash Offset, not just Corner Mode Windows. 3. b) Corner Window : Sash Offset is controlled by Corner Settings "Corner Condition > Mode : "Corner Post", only (!), although I don't use that Mode but Flush Glass. This is the only Mode to set an Offset - but determins Sash Offset in general, when Corner Mode active for any of that Style's Windows !
  3. Now that Styles have been rolled out for plug-in objects, I'd like to see Styles for an arbitrary groups of objects. Imagine a Group of objects, but in the OIP you get a check button to change it to a Style and check buttons for choosing which objects are part of the Style and which ones are just part of the instance (or some interface to choose them directly in the window). Or imagine a window object Style that can be converted to a generic Style using a similar process. So for instance you could have a Window Style but then add your own freeform modelled window sill to it. It wouldn't act like a Group, that can't be inserted into a Wall, but act like a plug-in object.
  4. Michael Gilbert

    Styles

    I have copied workspace and a file containing wall scripts that call wall styles to a remote machine. However, on remote machine when I open the copied file the wall scripts will only ever draw one of the styles contained in the copied file. If I compare the 2 Resource palettes the remote machine does not list the Wall Styles. Is there something really dumb I am missing - I thought the Styles would be contained in the copied file. The image on the right taken from local machine shows Wall Styles listed - see red box. But on remote machine listed in blue as per local machine but not under resources drop down menu. Any advice much appreciated. Michael
  5. 1. Where should i put things like Door/Window Styles in, when there are no Door/Window Style Folder types ? In Slab or Wall Style Folders ? 2. Can I rename "Standard Named" Folders to suit my own Naming Standards, rename these objects and move things around ? (Heliodon Symbols, Saved Views, and such ?) or will I risk things no more being found ? Or is that something that can be (fully solved) and needs to be solved by "Standard Naming" Options ?
  6. I have set up a slab style as shown in the below image. As you can see in the offsets have set the lower 3 to have a -200 offset so that I can draw conc blocks around perimeter. The style has worked fine for most applications. Have a growing need to the -200 offset to 3/4 sides with no offset to 1/4 side (Basically where the slab is adjacent an existing structure). Is there a trick to get the object to show offsets to selected sides only or is this a case of having to use a work around. Thank in advance.
×