Jump to content

SamIWas

Member
  • Posts

    287
  • Joined

  • Last visited

Everything posted by SamIWas

  1. Yep. Most likely the internals of the symbol are in the "None" class. This is very normal. "None" is the default class in every document (along with "dimension"). Your lighting symbol might be in the "Lighting" class, but the lines and polygons that make up that symbol are probably in "None".
  2. Yeah, that's a bummer. When I have some time, I guess I'll have to learn python scripting. I also can't use comma-delimited. Almost all of my data has commas in it. " Edison 12/3, 50' ". And I'd rather deal with working around it than changing all of the data to something uglier.
  3. Okay. Thanks all. I was hoping for something simple I was missing! Seems like that would be a bug, and one that could be fixed fairly easily.
  4. When importing a tab-delimited .txt data file from Filemaker, some fields may be empty. I've noticed that when a field is left black, Vectorworks ignores it and imports the next field in its place. So I have this test data: R1 1ABC 1DEF 1GHI R2 2DEF 2GHI R3 3ABC 3GHI R4 3ABC 4DEF R5 5DEF 5GHI And this simple script to test it: PROCEDURE ImportInfo; VAR filename,recnum,field1, field2, field3: STRING; BEGIN; Getfile(filename); Open(filename); WHILE NOT EOF(filename) DO BEGIN Read(recnum,field1, field2, field3); AlrtDialog(concat('Record: ',recnum,'. Field1: ',field1,'. Field2: ',field2,'. Field3: ',field3,'.')); END; {while} END; Run(ImportInfo); So, when I run that script, the first dialog says: Record: R1. Field1: 1ABC. Field 2: 1DEF. Field3: 1GHI as expected. But, the second run of it says: Record: R2. Field1: 2DEF. Field 2: 2GHI. Field3: R3 So, it has skipped the blank area in the first field of the second record. I have been dealing with this for ten years by putting a dash in empty fields. But, I really want to move past that, as that is error-prone. Since it seems to ignore the field, I don't know how to check for the field being empty. I can't move to comma delimited, and would really rather not move to colon-delimited. You guys are geniuses, so I'll throw this one at you!
  5. Yep...the way mine is currently set up is that is uses IsNewCustomObject() to generate an ID upon creation, looking at existing IDs and adding 1. Then when duplicated, it checks the ID against the object name, which changes no matter what. If those two are different, it changes the ID number. But, this will only happen upon regeneration, which requires changing a field. SO, for now, that's what I do. I'll have to look up how to deal with kObjectCreated/13.
  6. I am not, but that's precisely the item I am trying to disable. When I drop a fixture in, it often assumes basic mode, when my symbol is in extended mode.
  7. When I drop some of my symbols into a drawing, they appear to automatically assume a mode from the drop-down menu. I do not want this, as I have my symbols drawn with the correct information, and Spotlight appears to always put the other mode. For instance, when I drop in a Viper Performance, it assumes standard mode, while I am using extended. My symbol's Light Info Record uses the extended number of channels. This explains why my paperwork was all messed up last show! At some point, I did a replace of the symbols on the drawing, and the number of channels changed to the wrong mode. I do not want Spotlight to assume a mode. Yet I cannot find whatever setting may control this. It does not appear to be in the LIR. Any way to turn this off, or just something I need to change in my workflow? Is it something I set when I made the symbol?
  8. Whoa. That all sounds way above my head! But I'll look it up...don't know anything about the SDK or kObj type stuff. That's a shame. Was hoping for something more elegant than having to assign them upon export.
  9. Expanding functionality of some of my tools a bit further. I need each object created by the tool to have a unique identifier so that data can be imported and exported between Filemaker. I have created an ID field in one of my tools in which I create this unique ID upon creation of each object. This works perfectly currently. However, any time I duplicate an object, the ID field will not regenerate until I change another field, which kind of negates the purpose. I've been trying to use the workarounds shown in the IsNewCustomObject page of the Language Guide, but I can't seem to get them to work either until I specifically modify a field in the OIP. Has anyone figured out a secret to a PIO updating upon duplication? The Lighting Device tool does it, so it must be possible. And, while we're at it: I know how to make a field in the OIP not editable. But, how can I make the object name also not editable? Can't seem to find the right procedure.
  10. I'm not at my console right now, but can you have multi patched fixtures on different fixture layers in the console? I don't believe so. If you are creating your fixture layers from Position, as shown in your dialog, it will then try to patch your multi-patched fixtures on different trusses to different fixture layers, which I don't think is possible inside the console. That's why it works when you choose "All in one layer" or choose to define fixture layers by design layer, assuming all of your fixtures are on the same design layer.
  11. This is one of the many reasons that I mostly stick to Cinema4D for this type of thing. Much, much more control over lighting, and the ability to do exactly this.
  12. The few times I've used it, it seems to have worked alright. I've never been satisfied with the results though. I ended up writing my own exporter which handles multi-circuit fixtures, different rotation offsets, and effectively names things and separates layers in the patch without having to alter the drawing's classes or layers.
  13. Weird...this topic posted twice, and I updated (the other one apparently) to say I found the Export Vectorscript command handy. I will dig info out of that and use it. Forgot about that command until about three minutes after I posted the thread.
  14. So, I may have asked too soon. From the "Export Script" command, I can dig some info out. Will need to experiment to see what works and what doesn't. But, if anyone has a simpler solution, I'd love to hear it!
  15. I can use the Poly command to draw poly shapes...easy. Now, if that shape is complicated, it could be quite difficult to figure out the number and location of points. Is there any command which will take a selected shape in the drawing and convert it to the code necessary to redraw it from within a vectorscript?
  16. I can use the Poly command to draw poly shapes...easy. Now, if that shape is quite complicated, it could be quite difficult to figure out the number and location of points. Is there any command which will take a selected shape in the drawing and convert it to the code necessary to redraw it from within a vectorscript?
  17. What exactly is a "chunk"? Is that 63 submenus total over the entire workspace, or per top menu? I don't know why you'd have 63 submenus per top menu, so I assume it's over the entire workspace. If so, it's certainly possible that I hit that limit. I think I had only 8-12 submenus added.
  18. Yep. On 2014, 12015 and 2016, I rebuilt my workspace several times and always had the same issues. I started 2017 building my workspace from scratch, and barely made it halfway through before it started failing. Every script I write is tested first in a different menu before moving it into the Object Context menu, so I know the scripts themselves function correctly.
  19. Restarting Vectorworks and the computer has no effect. Once you get a certain number of scripts or folders in the Object Context menu, things just start breaking down. At first, just the first 20 or so scripts would work, while anything after that would fail. A week later, only ten would work. Now, nothing. Here is a copy of a simple script which creates a popup window to enter a channel for selected fixtures. For me, it's just much faster than opening "Number Instruments" or even double clicking on the fixture and entering the info in the edit fixture window. I used it frequently, then it just stopped. And so did everything else in the menu. I know the menu used to work, because I used to have an extensive Object Context menu. Now, I can't even use it. I have a support ticket from Service Select Support last year: And then again this year:
  20. You can't format database rows individually. The formatting is done in the header row. Is that what you're running into?
  21. I have several dozen scripts which I've written to greatly speed up my workflow doing short tasks which I may do 100 times an hour (mostly related to lighting fixture info, custom move and duplicate tools, custom selection tools, etc). They are divided into several folders in the object context menu. At some point, most of them just stop working. Currently, not a single one works. This was confirmed by VW to me some time a year or two ago. It's been happening since I believe 2014 and kills my productivity. Has almost made me question upgrading further.
  22. That did the trick. Thank you so much! Onward we go. Now, if VW would just fix the years-old bug affecting the Object Context menu, everything would be peachy!
  23. The SetParameterVisibility worked for me about 95% of the time. For some strange reason, sometimes parameters don't change visibility on the first change of another parameter. On the second selection of the same parameter to the same value, the visibility works correctly. Weird.
  24. I would love to be able to pay monthly for a program, but I'd want that to go towards full purchase. I really hate the idea of paying for software, then losing it completely once I stop paying a fee. At least with VW, even with VSS, if I ever cancel, I still own the last version forever. With adobe, it's pay or lose it, right?
  25. Thanks, guys. I will give those a try and see what happens. My tools are basically "point objects" which draw some shapes and add some text based on OIP input. I don't know what an "event enabled" objects are, so I can't answer that question.
×
×
  • Create New...