Jump to content

JBenghiat

Member
  • Posts

    1,799
  • Joined

  • Last visited

Everything posted by JBenghiat

  1. I think you’ve hit upon the solution. If you set the line to 0 line weight, it will also hide the marker. A line length of .01mm should hide itself in the marker.
  2. How are you exporting data? If you're starting with a worksheet, you can use the 'UID' field. File>Export>Export Lighting Device Data.. will always include the UID in the data file, as well as break out cells and accessories. If you're exporting via script, you can retrieve and write each objects UUID.
  3. That's correct, RunTempTool() will send you away from the menu command, so any data that you need passed from the menu to the tool needs to be stored in wither static variables or written to saved settings. If you're doing something like collecting a point and returning to a dialog, you need to rebuild the dialog data after running the tool.
  4. In your file, open Document Settings. You will see a preference for 8 light limit. Uncheck that. This was added so that files created in earlier versions render the same when up-converted (for better or worse).
  5. I believe this is only in shaded renders. Lit fog basically ignores shadow-casting objects.
  6. https://www.vectorworks.net/support/bugsubmit Including your file with screen shots or movies and a way to reproduce if possible will provide the best opportunity for the bug to be resolved.
  7. import vs vs.DSelectAll() universe = vs.IntDialog("Enter a universe number", 1) vs.SelectObj("INSYMBOL & INVIEWPORT & ('Lighting Device'.'Universe'='{}')".format(universe)) Note, best practice is no semi-colons. with each instruction on a separate line
  8. @mjmLooking at the screen video, you might just be seeing Savvy Select Similar working as designed. When you hover over a Lighting Device with Accessories, you'll see hot spots for the accessory. In the case of a C-Clamp, it will be right over the origin. The magic wand cursor will also turn blue when you're about to select accessories or cells. Not only will Select Similar detect the cell or accessory, it will also set the OIP to view data for that matching items (in your case all the accessories that match that position).
  9. Unfortunately this is not possible. In my opinion, Schematic Views aren't quite in synch with professional standards and workflows and could use a set of enhancements to be truly effective. I'd recommend posting this to the wishlist.
  10. ISDK::RunTempTool() will run a tool by command. You have to build your own VWExtensionTool, but that offers you complete flexibility with how the tool functions.
  11. No, the visualization palette does not support any kind of grouping. With the "current scene" option selected, it will only show lights in visible layers and classes, so you could, for example, show only lights in an active class.
  12. Yes, VW writes preferences to disk on close. This sounds potentially dangerous— using SetPref calls to make the changes you want is probably a better option anyway.
  13. SPL only two areas of control - the position name (which can also be custom text), and the note overall, which is via text styles. Unlike AP Truss Tags, SPL objects only display the data as part of the object, so there’s not any extracted data to work with further.
  14. If you want a count of all the components, use the List function. For example: #List#:#TrussItem#.#Length# for a list of lengths #List#:#TrussItem#.#Symbol# for all the symbol names #List#:#TrussItem#.#Name# for all the true item names
  15. Yes, Savvy Position Label will attach directly to truss objects and report on the entire truss system, a truss line, or a single truss piece. You can list total weight and length, as well as list component pieces or attached items.
  16. Savvy Position Label will provide counts and summaries. It traverses truss systems or truss lines in ways that are not possible with Data Tags. https://benghiatlighting.com/software/product/position-label/ @Sam Jones's AutoPlot has a truss tag object, which may provide some summary information. https://autoplotvw.com/index.htm
  17. Are these just a line of light objects in Spotlight mode? Can you share the code where you apply the color?
  18. @Pat Stanford I explored the various responses to Date() several years ago for exactly that purpose. I can confirm that the formats depend on localized settings as well as Mac vs PC. You can get the date in various formats, and make some inferences, but it’s messy and if the user does any kind of custom settings, it breaks. Yes, the Python date functions are in a module, but it’s built-in, so you don’t need to package it with your script. And if you’re running Python from within VS, it all gets encrypted without doing anything differently. The one thing to flag is that the SetVSVar() call breaks in an encrypted script — use the string repository (Rpstr) commands to pass data between languages. Not only will Python let you get the correctly formatted date, you can just diff dates to get the elapsed time span. Between that and the hoops you have to jump through to guess the user’s date format settings, the overhead is way less than an all vs solution.
  19. It is. I highly recommend using python's date functions — even if you end up passing the python to VS, it's still worth the modern date features.
  20. https://riptutorial.com/git/example/7327/diff-utf-16-encoded-text-and-binary-plist-files
  21. One thing to check: Go into Spotlight Settings, and then parameters. Find the symbol name, instrument type, and device type rows. Make sure there is a check mark in the accessory column. This tells Spotlight that Lighting devices and their accessories should have discrete data for these fields. I had a few files that, when unconverted, had the instrument type unchecked, which caused all sorts of issues when adding or converting accessories.
  22. I don’t think so. You have to use a two-button radio.
  23. Shameless plug for Savvy Sequencer. You can number any data field in a symbol or plug-in, as well as data tags or just plain text blocks, the latter which can be optionally grouped with the objects they number.
  24. That would get me into the profile group, but I want to get the properties of a render light in the profile group without the user seeing the other stuff I store there. Basically the equivalent of right-clicking on the light in Visualization and choosing edit. So far, I get the entire plug-in in the properties dialog, not the object passed to EditObjectSpecial.
  25. You can also just use SetTextSize() after you create the text block, and not worry about the document settings.
×
×
  • Create New...