I realise that not all PIOs can be programmed with VectorScript and of course I don't even care.
However, default values of parameters (including choices of pop-up lists and radio buttons) should be editable by users; same applies to OI labels (alternative names). Eg. the Plant tool is a disaster in its assumptions.
Why can't there be a VSO "front end" which would use something akin to the $INCLUDE instruction of VS to invoke the "vwtool" or whatever the clever bit might be called?
As PIOs get more complex, I anticipate that we'll see even more of these user-unfriendly thingies. (I seem to recall a statement by Robert Anderson some years ago, saying that all future plug-ins would be written with VectorScript; the huge advancements of VS since VW 9 are a testimony of some sort.)
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.
Question
Petri
I realise that not all PIOs can be programmed with VectorScript and of course I don't even care.
However, default values of parameters (including choices of pop-up lists and radio buttons) should be editable by users; same applies to OI labels (alternative names). Eg. the Plant tool is a disaster in its assumptions.
Why can't there be a VSO "front end" which would use something akin to the $INCLUDE instruction of VS to invoke the "vwtool" or whatever the clever bit might be called?
As PIOs get more complex, I anticipate that we'll see even more of these user-unfriendly thingies. (I seem to recall a statement by Robert Anderson some years ago, saying that all future plug-ins would be written with VectorScript; the huge advancements of VS since VW 9 are a testimony of some sort.)
Link to comment
2 answers to this question
Recommended Posts
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.