Jump to content

migrating plugins to a new version of VW


Recommended Posts

hey guys,

 

this year is the first year that i have developed plugins for VW and I'm curious to know the process of getting plugins ready for new releases. i have about 10 plugins that i've made that i will need to move from VW2020 to VW2022.

 

also wheres the best place to see whats new (in regards to plugins) with the new version. 

Link to comment

Check the Vectorscript Function Reference. One of the sort options is By Version. Take a look there and see what is new and what has been deprecated.

 

This does not appear to be available on the Developer site, but only in the local version.  

Applications:Vectorworks 2022:VW Help:Script Reference:ScriptFunctionReference.html

  • Like 1
Link to comment

Following on from this, a question about the actual plug in files themselves (VSM,VSO etc).

 

Should these be backwards compatible with previous VW versions? Or do I need to distribute them in the oldest version I want to support and then when the user first runs the command it will automatically update it to the latest version?

Link to comment
On 9/28/2021 at 1:06 AM, tbexon said:

Following on from this, a question about the actual plug in files themselves (VSM,VSO etc).

 

Should these be backwards compatible with previous VW versions? Or do I need to distribute them in the oldest version I want to support and then when the user first runs the command it will automatically update it to the latest version?

 

 

From my experience, any plugins created before the latest version work with the latest version -- IF -- they are not using depreciated function calls (alot got dropped in 2012).

But if you're wanting plugins to be backwards compatible they have to be created/edited in that version to work with that version.

 

E.g

You create a plugin in version 2018, and then come 2021, a new version gets released and all should be well (from what i know, no functions were depreciated in 2021).
However, once you make any edit to the plugin using the plugin manager, under 2021, (eg add a parameter, remove a parameter, change a parameter name, etc), that action breaks backwards compatibility. If you point your script to an external source and are changing script code in an external editor, this doesn't seem to affect the *.vso or *.vsm files.
So if you are want to do edits to the plugin via the plugin manager and still maintain the backwards compatibility you'd have to do it in the earliest version (in this case 2018) you want compatibility for.

Again, my own experience. 

 

Edited by twk
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...