Jump to content

Stephen Sorenson

Member
  • Posts

    27
  • Joined

  • Last visited

Everything posted by Stephen Sorenson

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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.
  16. 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.
  17. 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.
  18. 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
  19. I did test the send to front and send to back in a simple object in an object node and they seemed to work as expected. Did not test the other two. After further testing I have found some weirdness with them, must be what you found. They move forward/to front seems to not work sometimes (which is odd because it's the first one I made and it seemed to work consistently) and the move to back/move backwards only works in an object node or wrapper. I think it might be sending to front or backwards before the other objects are created which might be why it only works in one direction depending on the object. I'm going to leave it here for now, see if I can get it working, but put a caveat on the original post. Currently I'm trying to get insertion rotation to (a) show up in the OIP and/or (b) find a way to get that information so that I can reverse rotate the text so it is always right reading.
  20. So, I made a couple nodes to help (send forward, send backward, send to front, send to back). Also hidden in my original boom file is an add surface node that I made to accomplish the bottom of the pipe being rounded. The move backwards/move to back seems to only work in the object node or wrapper, and the forward/front was working, but on further testing couldn't get it to work consistently. I'll keep working on it, but it may be one set of nodes will work in one drawing and the other set will work in another. So I'll leave these here for now with the caveat that they haven't been working consistently.
  21. I've also experienced this on both Windows and MacOS with the all the listed, plus the accessory insertion tool. It's most problematic for me when using middle mouse button boomerang pan as I have to sit and wait for it to switch back to the insertion tool each time (and it's a good 5-6 sec). So if I have to pan 3-4 times it takes 20+ seconds to get across the drawing depending on my zoom level. I don't even use the symbol pull-down menu, is there a way to just disable it? *edit - I imagine it probably goes faster on an SSD. Both machines I tested on are HDD.
  22. So I've found a crash in spotlight when importing symbols (when you import their containing folder and they reference another symbol). I didn't find this issue already listed in the forums. Found this issue in the Lighting ETC folder. When you right click in the resource browser to import (for instance) the S4 Par folder, it imports the symbols and the body, but when you edit the individual symbols (Source 4 Par NSP, etc.) the body doesn't show up (it also doesn't show up when you insert the instrument into the drawing). When you drag a selection box around the missing symbol vectorworks hard crashes to desktop. The workaround seems to be selecting the instruments inside the folder and importing that way instead of importing the folder itself. This only appears to affect instruments that reference another symbol inside of them. If you save the file and reopen it after import it appears to delete the reference to the body symbol completely (so no crash, but you're missing the body symbol).
  23. Alan - thank you for your input! I was trying to achieve something specific (which is mostly controlled by our workflow at my office for my day job - hence all the complicated inputs - they were features requested by the rest of our drafting team). It also has to work in object mode for some of our less experienced drafters - I'm dropping it into our corporate symbol library. The boom label is so our on site techs know what size boom we're using, and I was trying to replace our folder of about 10 different size towers (and every time we wanted to update something we had to go through and update all 10 symbols). By the way I think the reason the rotation didn't work properly is because it was passed through to a group. I tried sending the circle and rectangle directly into the rotation and it worked in object mode. Haven't gotten the loci to work yet through the object mode in your version, but if I do I think that the rotation after creation that you've done will probably update faster than the way I did it by offsetting from the top - I notice a delay in mine that doesn't exist in yours. I think I will incorporate the div/size/series sequence to create the number of loci. That will get rid of one of my input nodes. I also remembered how stupid imperial measurement is once again. Would make things a lot easier for display. I have to say that I've been so excited by this project that I'm working on it on the couch on my day off. Thank you for the kind words regarding my lighting designs! I don't do much lighting rendering in spotlight on my home computer - it's a bit too resource intensive for my 4 year old macbook pro, but I do all of my plots in it. I work part time during the day for an event company and then do my own theatrical designs on the side and in between.
  24. Hello, I've been very excited to get started playing around with marionette. My goal was to start with a fairly simple project to start learning, and something that would work for our company (we have to create 2d plots quickly (utilizing mostly booms). This is hopefully the start of a number of objects I'll be able to create in Marionette. I have a *little* bit of python experience which has helped a ton. There are a few bugs that I know of - the text field doesn't work well with booms that are fractions of full feet, but for our purposes we only do booms that are full feet anyway so it's lower priority. I want to organize some sections of the script into wrappers since it's a bit messy at the moment. I'd love some feedback if anyone has any thoughts on a better/more efficient implementation. Thanks!
  25. I've noticed that in VW2011 I have to draw a fairly large selection box around the units to select them. I'm curious if this is a known issue, or if I'm alone, and if someone has a possible solution to this. I couldn't find anything else on the board about it here, but I'm not sure how many here are using 2011 yet. I'm using SP1 because of the accessory issue I ran into in SP2 (accessories not aligning themselves properly in 2d with the lights - my scrollers were about 18" to the left of the front of the unit and at about a 35? angle as an example- reverting to SP1 solved this issue for me). I tried it in the brief time I had SP2 installed and I had the same issue. Also tried with blank document. I'm using the new set of symbols that came with VW2011 (also my alterations of them - but for my test I just used the default VW ones). Any help would be appreciated.
×
×
  • Create New...