Jump to content

_James

Member
  • Posts

    374
  • Joined

  • Last visited

Posts posted by _James

  1. Dates on that presentation were:

     

    10/01/2023 - SP3

    14/03/2023 - SP4

    16/05/2023 - SP5

    18/07/2023 - SP6

     

    I thought I had posted a screenshot to the forum but I can't seem to find it now. I think they also mentioned that they would do SP7 and maybe 8 if required, but these would come after VW2024 was released.

     

  2. I use dividers on my projects and never (intentionally) re-sort the design layer order. I appreciate other people do though!

     

    A non-workaround way to add dividers would be nice. And one that is impervious to the accidental purge (which I often accidentally do as they are always empty).

    Personally I am less interested in folders as it just resorts to lots of clicking.

     

    I would also be happy to stop calling them design layers and sheet layers and instead just have layers and sheets as has been mentinoed.

     

    (Whilst we're at it, lets get rid of design layer scales too...)

    • Like 1
  3. Data tags are great, but sometimes I find the workflow too inflexible for annotating drawings. To get the right data you would like, you need to create the tag style and set it up in advance.

     

    I wonder if as an alternative approach, there could be another mode of the Data Tag tool that when you select the object you wish to tag, all the available data is displayed and you can select the relevant fields you would like, bundling them into a new tag on the fly. You could then choose to have this as a style or leave it unstyled.

     

    This means that when you are annotating things, there is minimal interruption. You don't have to stop to make a new style (or think in advance that a new style is required), and it's also much more flexible. Sometimes you don't need a new data tag style for every single thing (don't get me wrong though, the styles work very well for often tagged objects). As someone who looks after VW in a small office, you don't have to second guess all possible permutations of how colleagues will use it and set up a tag for them to use. 

     

    This was in my mind when annotating some steel beams recently, where on some pages you just want the "Steel Section", on others you may want to have the "Steel Section + Beam Reference Number", and on other sheets you may wish to have "Beam Reference Number + Section + Note such as *to Structural Engineer's specification*". I think it's a bit cumbersome to have three separate tags, or to go to the effort of making three separate tags when they may only be used once each.

    • Like 1
  4. 6 hours ago, Matt Overton said:

    The way it's been talked about I though it would be monthly not bi-monthly.

    I had also expected a few more and perhaps not so structured. I had inferred that "when it's ready" meant when the features are ready, this is still saving features for a wider release; if a new feature is ready in the second week of January it won't be released until March.

     

    This is still a big improvement however on waiting until September, but I guess I was a little underwhelmed having gotten carried away with the notion of having a very quickly evolving software and you feel that change is implemented quickly rather than having things rattle around the forum for years before anything happens. A software that updates every week might drive me insane - but it does reinforce the idea that it's being constantly improved.

     

    Again though, hopefully a big improvement and I will wait and see what Vectorworks come out with in the near future (SP1 should be out today if that graphic is correct!)

  5. Another couple of things to add to this (I can't figure out how to edit my post to add it to the list).

     

    6. Better management of Notes

    Our database quickly became unwieldy. It would be good to have some kind of manager where you could see where notes are used and if any in the database are completely unused. A purge option would then be good to clear out outdated notes that are no longer relevant. I have seen the "Reconcile Notes" window which is pretty good, but it seems a bit tucked away. In my view this should be part of the Notes Manager.

     

    3. Notes Manager - Have Databases as a Resource Continued..

    Also just wanted to reiterate how much of a drag the constant detachment of the database from the file is. I think there should be the option to have the notes stored within the file so there is no link to a distant file somewhere which in my experience is not very resilient.

  6. Thanks @Wes Gardner,

     

    This gets part of the job done (the "colouring in") but do you know of anyway to make generate the descriptions in an easier way than manually typing things out? Data Tag or similar? Maybe using the new graphic legends to generate a wall schedule, but then there likely isn't a way to link this to the colours of the data visualisation?

  7. On 8/13/2022 at 8:23 AM, Boh said:

    updating of a note in a database can mean that any notes in unopened files linked to the database will lose the link.

    This is a big problem.

     

    For me, the whole point of having a centralised database (project or otherwise) is to quickly deal with changes that happen through a project, particularly important now with supply chain issues meaning there are many material changes due to so many things being on long lead times or out of stock. It should be able to handle a change in the database and change, or warn you that there are changes and ask you to confirm them on opening the file.

    • Like 1
  8. Thanks everyone for the messages and advice. @michaelk was right when he said in his webinar that this is one of the nicest places on the internet! I thought it would be a clear win for Python but Vectorscript seems to still have advantages.

     

    I was partly inspired by @MarcelP102 and his thread "Babysteps into Vectorscripting". I'm a big believer in learning by doing so I need to get my teeth into a project!

    • Like 1
  9. I would like to get into writing some scripts for VW either via Vectorscript or Python. I have pretty much zero experience save for a few modules of "Automate the Boring Stuff with Python" on udemy or similar platform. I was wondering if anyone had some tips/recommendations on how they got started and what they found helpful/not helpful.

     

    - I've watched this Vectorworks University course about Vectorscript which is a great primer to show you what is possible, but now I'd like to jump in and actually make something.

    - I will try to take a look at the Vectorscript Language Guide here in the next few days

    - I've been having a look through https://developer.vectorworks.net/index.php/Main_Page and the Vectorworks help pages.

     

    I'm leaning more towards Python for it's use outside of Vectorworks, but I do recognise @michaelk's point about Vectorscript having some advantages (like with the compile button, exporting objects as script to get the creation data etc.), so i'm interested to hear people's opinion!

     

    Thanks in advance!

    • Like 1
×
×
  • Create New...