Jump to content

Sam Jones

  • Posts

  • Joined

  • Last visited


501 Spectacular

Personal Information

  • Occupation
    Technical Director
  • Homepage
  • Location
    Los Angeles

Contact Info

  • Skype

Recent Profile Visitors

10,578 profile views
  1. One, make a list of the data you want collected for each breaker. Ideally, it all comes from Lighting Device parameters or is computed from those parameters. That will give us the worksheet Two, carefully layout the data for each breaker, spaced to land under each breaker. Each breaker will get a label, but it would be possible to define those labels to be printed as a group on one long label like OnLine 2530 or OnLine 8500. "One" and "Two" can be done separately. "One" will be needed for the script that makes the universal worksheet. "Two" will tell us how to layout the label(s) that use the worksheet. An interesting idea, but I think creating labels for the breaker row of a specific rack is a safer and probably easier way to go. If you have another rack, with different spacing make a label for that rack. One would not need to have more than one worksheet to service all the labels. One label design per specified distro or dimmer rack allows all the measurements of module width, spacing, number per row and other groupings to be baked into the label.
  2. The worksheet cannot be created without a script, but the script is pretty straight forward data collection. Such a script should collect all the data that one might want to list under a breaker in a worksheet row. Different people would use different data for different racks. It would not matter what cell held which information, because those cells would be assigned to label fields, just like the truss tape worksheet. The same worksheet could be used for differently formatted racks that use differently organized breakers; just pick the appropriate label for the appropriate rack. Save the different labels by rack name. The big trick would be the rack header that is at the top of your example. I would be tempted to make a worksheet/label combination that just printed rack headers, but there may be alternatives to that. I retired, and I don't generate labels for anything; I just help people do it with plug-ins. Help with rack and distro labeling is often requested. I'll do it, but it would require a significant input from users (you). I need data specification, the data you want and how you want it, and specific rack breaker space dimensions and/or specific label choices and label formatting of the data. If you want to do it, I'll go there (also true for anybody else), but there will be some significant back and forth. Usually, responses to me about this sort of thing die on the vine; nobody has the time. The goal here is to create a script for creating the worksheet, and then creating the appropriate labels. Of course, you wouldn't have to print on labels; you could print on regular paper and cut it up. I can't even get riggers to give me simple examples of the labels they would need, and that is after I volunteered to create the labels and the appropriate worksheet creation commands.
  3. @Cookie_NZ Is the Excel sheet printed on label stock, or is it printed on regular paper, cut up, and taped below the breakers, or not cut up and taped to the rack? Are the Excel sheets generated separately on a per rack basis, or is an Excel sheet generated that contains all racks?
  4. @Cookie_NZ if you can provide a worksheet, I can provide a way to print the worksheet cells onto Avery or Online labels. Let me know if you want to Zoom.
  5. I want to import a record, and if the record already exists, I want to check the number of fields in the existing record with the number of fields in the importing record in the callback procedure of "ImportResToCurFileN". Since both records will have the same name, how do I do that. Getting a handle to each and using the "NumFields()" function would work, but since the records have the same name, how do I get a handle to each or is there another way to query the number of fields in each record definition of the same name? How does the callback procedure specify whether or not to import the incoming resource? TIA.
  6. Good luck. I don't know how data tag would access the piece count, but perhaps a tag wizard will share. I'm pretty sure Josh Benghiat's "Savvy Position Label" will do the job, and below is an example of an AutoPlot Tools, "Truss Tag". The graphic arrangement can be customized; I assume that is also true for the Savvy Position Label.
  7. @JBenghiat Josh, can one make a worksheet of Savvy Position Labels and get counts and totals from that?
  8. Nope. I imagine the plug-in command would create the dialog with a pop up menu. I imagine you could tab to the pop up, but I'm not sure the arrow keys will travel the choices, but maybe. So, 1. select a hoist 2. initiate the command which shows the dialog with a pop up. (the dialog has to create the list of lengths 3. tab to the pop up 4. arrow key to the length 5. hit return 6. the command code writes the choice value into the field of the custom record. I think it would be easier to code just a query for the length that is then written to the record. compared to making the dialog and processing it, the ease in coding would more than make up for the typing of the length HoistHandle := FSActLayer; {assumes the hoist in on the active layer} LengthStr := StrDialog('Input cable length', ''); SetRField(HoistHandle, recordName, fieldName, LengthStr)
  9. No help here. I haven't a clue. I'll go out on a limb and say VS is not up to it, but would be delighted to be shown I was wrong. I started listing a bunch of issues here, but it got crazy. Why do you want to have this functionality? How would you like to use it? @MullinRJ have you got a magic vector math solution?
  10. Not really. 10 years ago I put 4 lights on separate circuits, 3 of which had the same unit number but different positions, on the same channel to make a path. Happens rarely, but does happen. Position and Unit Number would be unique, and would have the additional advantage of telling you where the fixture is. That doesn't matter with this problem, but the use of channel numbers to identify fixtures drives me crazy. Where the #$@&! is channel 203? It's not coming on, and the programmer wants me to troubleshoot it.
  11. As of 2024 VW has native rotate each 90° commands, but my users never bother to notice.
  12. Actually, it will place the symbol at the insertion point of the PIO. The insertion point is where you click when you place the PIO. If you want to offset the symbol from where you click, put the amount of offset in the Symbol() call as measured from the click.
  13. Yes it will. It is part of AutoPlot Tools for Spotlight. You can contact me, sjones@autoplotvw.com.
  • Create New...