Jump to content

Stephen Sorenson

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stephen Sorenson

  • Rank

Personal Information

  • Occupation
    Lighting Designer
  • Homepage
  • Location
    Chicago, IL

Recent Profile Visitors

405 profile views
  1. I'd be so happy if I could start a new multi at B1 without reopening the number instruments window.
  2. Stephen Sorenson

    Dialog Builder 2018 Tools

    Having built all of my dialogs by hand up to now I decided to finally give the Dialog Builder a chance, however when I run the EnableDialogBuilder command it seems like all of the tools aren't populating the palette(see attached). I'm on 2018 SP3. Anyone else have this issue or know of a fix or something I'm doing wrong? I've tried restarting vectorworks, my computer, and running from a fresh workspace. I haven't tried another computer yet.
  3. Stephen Sorenson

    Modify instrument by color not working for class specific containers

    Yeah, use label attributes I've see use the pen color you set the text to in the edit label legend layout as the pen color for the container (but not the fill color). Use symbol attributes should use whatever is saved in the container symbol and I've never had a problem with that one. Obviously now I'm having issues with the Use instrument attributes... this tool has always been a little trial and error for me every time so I tried to double check every setting 3 or 4 time before posting here. For reference here's the same setup in VW2017 and the containers changing how I would expect.
  4. When setting the modify instrument color to only a specific class and setting the label legend container to use lighting instrument attributes it would still color that class in the container field. (I set a copy of the container in the container symbol to use a Symbol-Color Code class so that only the channel oval fill would be color coded. I went back and tried at it's most basic level using the color field (image attached) in a brand new document and even when set to the default container class of 'None' the color coding doesn't propagate down to the container. It still propagates down if you don't modify by class but I don't like to change the color of the instruments themselves, but I like a visual identification of system locations (specifically for a designer I draft for). I used to do it with a label legend per system (using different containers) and I'd prefer not to return to that method. DId a workflow method change? I've even opened up a 2017 drawing in 2018 and the color coding that worked in 2017 doesn't come through. This is on Spotlight 2018 Service Pack 3 Windows 10.
  5. At least according to what I read over in python scripting forums it seems that to utilize plug-in styles you have to have a hard coded number in Vectorworks to access that feature. As someone who makes custom plug-ins (in the python environment) it would be helpful to be able to access that feature in it's entirety for the plug-ins I've made so that the custom plug-in workflow better matches the rest of our Vectorworks workflow.
  6. Stephen Sorenson

    Plug-In Styles

    Well that's unfortunate, but good to know so I don't waste any more time trying to get it to work - Thank you! I'm going to put in a feature request.
  7. Stephen Sorenson

    Plug-In Styles

    I've been struggling with this one for a while. I'm trying to properly implement plugin styles from inside a python script plugin and while I've been able to get the style dropdown menu to show up in the OIP (and it will save a plugin style to the resource browser) I can't seem to access the naming/edit features. It seems there is a default edit plugin style menu that's accessible (at least if I'm reading this correctly). http://developer.vectorworks.net/index.php/VS:AddToPIOStyleEdit I have a feeling it might relate to this but I'm not quite sure how to implement it properly. kObjectEditPluginStyleByDefault = -10 I don't know if all of the functionality is available to vectorscript however or if I'm barking up the wrong tree with this.
  8. Stephen Sorenson

    Checking Type of Variable

    by putting 123 in quotes you are telling python to regard it as a string. Also for the message dialog I believe you have to convert to string so this code should work: import vs number = 123 vs.Message("Type=" + str(type (number)))
  9. Stephen Sorenson

    Scale Object

    I had a few hours this morning and I realized none of the current plugins I've created support dimension localization, so I've taken a quick crack at it in a very basic form in starting to create a custom scale plugin (for theatre prosceniums and US/DS Scales primarily). Eventually I intend to add more customization but currently I'm making sure of functionality before I start adding features. The localization seems to work, however as I don't generally work in non US units I'm concerned I may be missing something. Any feedback would be appreciated. When I'm finished I'm just intending on dropping this into resource share and/or the spotlight section of the forums. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ScaleObj.vso
  10. Stephen Sorenson

    Getting a unit record field from a custom plugin object

    Thanks Josh! ValidNumStr appears to work for my application (in early tests). And thanks for the recommendation on Eq() as 1' seems to want to come back as 11.999... Steve
  11. So I'm working on a custom dialog script to select various plugin objects I've created by type. I'm using vs.GetRField to get data from my 'Diameter' field, but since it's passing as a string interpretation (6'0" shows up as 6e000') it's not in a usable format to match to my incoming data from the vs.GetEditReal function (which shows up as 72.000000). I'm wondering if there's a function I'm not seeing or finding that will get that info in the units format like I need. I couldn't seem to get vs.GetObjectVariableReal to work for me either but perhaps I'm using it wrong. I figured the index value would be the number (or n-1) in the plug-in definition parameters.
  12. Stephen Sorenson

    Marionette OIP ordering bug

    Hey Alan! Yeah, I was just using the built in nodes to properly notate the bug (so that it couldn't be traced or thought to be the fault of a custom node). The bug remains no matter what input you change to have a number as a leader - so if you try to order your object info palette this bug seems to crop up (it also happened when I put a number in front of the Dim named input). You are correct, it does keep it for one version if you open up and then copy-paste, but as soon as you change a value it reverts on duplicate to the defaults in the object. I submitted a question about this during the webinar this morning and got a personal reply to submit a bug report, so I did as it sounds like it's not working as intended.
  13. Stephen Sorenson

    Multiple Extrude

    I like the ordered list much better for most applications - that's a great solution. The send to front, send to back nodes only seem work if the object you are sending in front of or behind already exists and I can't seem to figure out how Vectorworks determines in what order things are made in the script tree. So it is of limited use and I hadn't thought of using an ordered list at the time.
  14. Stephen Sorenson

    Marionette OIP ordering bug

    I've submitted a bug report, but I wanted to share here as this has caused me a lot of headaches trying to figure out. Trying to save other some headache as this caused a big one for me. (Unless I'm completely off my rocker and something else is happening here). If you number the inputs on a marionette object in order to order them in the OIP, when the resulting plug in object is duplicated (after changing the value) the new object reverts to default values. As far as I can determine this action relates specifically to prefacing the name with a number. and only occurs with Marionette PIOs. 1. Insert an input node (real or int or I've created a document rotation value input node) 2. apply to rotate object in the marionette network 3. Name the input with a leading number to order it in the OIP 4. Convert to object node 5. Enter a new value in rotation 6. Copy paste/duplicate the object with the new value 7. New object will revert to default values. I've attached an example of what I mean here.
  15. Stephen Sorenson

    Pop Back Node

    It's useful sometimes to look at the python descriptions for some of these commands, as pop comes from the list structure command in python. So pop back actually removes the last item in the list and the key is returns it (so it gives you the value). So what you get back is a new shorter list and the last value in the list. The list could be a list of points, text values, whatever. https://docs.python.org/3.1/tutorial/datastructures.html