Jump to content

Stephen Sorenson

Member
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stephen Sorenson

  • Rank
    Greenhorn

Personal Information

  • Occupation
    Lighting Designer
  • Homepage
    sorensonlighting.com
  • Location
    Chicago, IL

Recent Profile Visitors

464 profile views
  1. Stephen Sorenson

    Modify instrument by color not working for class specific containers

    This feature is still broken in 2019 Service Pack 2, I had hoped it would be fixed with the new version.
  2. @Nikolay Zhelyazkov Thank you, that's exactly what I was looking for. I still had to keep my for loop to put the project data in each individual title block's project data record in addition to the Project Data format. I already had a ResetObject (and an HMove(h, 0, 0) for good measure).
  3. So I have a custom script that I've created that works in concert with the Vectorworks Title Block object. I import info from a csv file exported from our database and it loads in fields like sales person, venue, event name, etc into the title block (via Title Block Project Data.[record field]). It also creates/updates version numbering (outside of VW revision data which is difficult to work with via script for what we're trying to do) and puts the initials of the person who most recent revised it into a drafted by field. I had to make some edits for it to work with 2018 last year, but got suitable workarounds for the issues I was having, but they've gotten worse in 2019 as I'm working on our transition. It seems that when I update the Record field it updates the title block visually, but the old information is retained "somewhere". Previously it was only an issue if I replaced the title block (it would load default data into the fields unless I had subsequently edited the title block via the project settings - but I would only have to edit one field and it would flag all of the fields as changed. Now if I edit only one field via the built in settings it will only update that one field, but all others will revert to the previous state. I was wondering if there is some way within the script to flag those fields as changed/edited so that they don't revert if I (or any of our other draftspeople) change anything via the built in editor.
  4. I'd be so happy if I could start a new multi at B1 without reopening the number instruments window.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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)))
  12. 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
  13. 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
  14. 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.
  15. 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.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×