Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by t-bud

  1. I finally got a response from Support in regards to this issue.  Thanks to a friendly Beta tester, for poking them about this, since their only response to me was to look here for custom scripts.


    Here is the response from support, that was helpful.



     Instead of changing the symbol name the user must now change the "Symbol Definition" parameter, lighting device symbols now rely purely on symbol internal indexes. Instead of symbol name the user should use the InternalIndex of the symbol. This can be found easily using the "Name2Index" function: https://developer.vectorworks.net/index.php/VS:Name2Index


  2. I have scripts that I have used for years, that change the symbol of Lighting Devices within the process of the script.  They are no longer working properly in VW 2022.

    I am using SP2.1 on a Mac running OS 10.15.7 (Catalina).


    The attached script should change the selected units to a 14deg unit.  The symbol for the 14deg is in the resource manager, and you can see with the debug, that the field value for the 'Symbol Name' has been changed, but it remains the old symbol upon completion.  However, the drawing is not updated, and in the OIP the symbol name remains unchanged, or is internally reverted back to its previous string.


    What has changed in VW22, that this doesn't work anymore?  Is there a 'Proper" procedure that I am not using with Lighting Devices?

    PROCEDURE ChangeSym;
    	SymNameStart, SymNameEnd	:STRING;
    PROCEDURE replaceSymbol(objectHandle	:HANDLE);
    	SymNameStart := GetRField(objectHandle, 'Lighting Device','Symbol Name');
    	SetRField(objectHandle,'Lighting Device', 'Symbol Name', 'Light Instr Prolights EclipseFS 14deg');
    	SymNameEnd := GetRField(objectHandle, 'Lighting Device','Symbol Name');
    	ForEachObject(replaceSymbol,Sel = TRUE);


  3. This may have been asked in the past, but I can not find it.


    Is there a way to modify the information that is shown in the Rack Elevation?  Like using a device legends used in the schematic? 


    I would like to be able to have User defined Parameters mapped onto the 2d representation.  For instance, I would like to have the IP Addresses of network devices be able to be displayed on the elevation. As well as be able to globally set font type, size, and location on devices.


    It would be really slick, if custom Parameter field names between Device and Equipment matched, then the data would be copied into the Object Info for the Equipment Item, when "Update Rack Elevation" is performed. I.E. if a custom Parameter labeled "Custom1" is active and defined for both the Device, and the Equipment Item, then data from that field would be copied from the Device into the Equipment Item, at the time of Update/Creation 

    • Like 1
  4. I would love it if devices were offset vertically, rather than horizontally when running the "Update Rack Elevation" command.


    It would also be really nice if Rack elements were more actively linked to their schematic counterparts.  There aha been a few times that I have needed to change the naming convention of components in the schematic layouts.  the names of the Elevation items is not updated, and the Room/Rack/RackU information is no longer linked back to the schematic device, and hence the attached Circuits.


    I have not installed 2021 yet, so maybe these are resolved with that release.

  5. Looking to create a report that would show each device, listing each socket in the device(connected or not), and if there is a connection, information from the circuit that is connected to the socket.


    Below is an illustration of report columns.


    Device.name | Device.model | socket.name | socket.signal | circuit.number | circuit.cable | circuit.cable length


    Does that make sense?


    What I am trying to do is create a report that will allow me to quickly see what is connected to each device, where ports may be available, and create panel labels listing what is connected to each socket.

  6. Is there a way to create a report that will list all devices, and what is connected to each socket of that Device?  


    I know I can do a Circuit report sorted by Source Device, but I would like a way to be able to get over information from the Device that is not included in the Circuit Record.


    Or maybe a way to map information from source devices into user fields in Circuit record

  7. I have some scripts that place data into Lighting Device Parameter Fields.  


    WIth VW2020 SP2.1, the changes do not seem to be written into the .XML for export into Lightwright.  I have to do a complete export for the updated information to be sent to LW.  


    I did not notice this behavior in VW2019.  Is there a function that I need to call now for VW to register the changed data for inclusion in the .XML?

  8. What is it about Lighting Devices?  I just moved 79500 instances on hybrid symbols, with a record attached, that are not defined as "Lighting Devices" to a different layer.  They were ungrouped, and the symbol is very similar to what I moved as a lighting device.


    This move took < 1.5 hours.  I don't have an exact time, as I went to lunch while it was working, and it was complete upon my return.

  9. Pat, that did help.  


    Yesterday I moved about 1600 devices between layers, and it took over an hour.  by grouping, I was able to move the same units between layers in only 3 minutes.


    Of course these devices hav no label legends attached, so I am sure that is saving some time.


    Do you have any trick for changing record fields for large numbers of devices? That seems to be another major time suck when dealing with a couple hundred devices at a time.

  10. I have a drawing I am working on, I currently have 38853 Lighting Devices, that I am trying to move to a new layer.


    The lighting device consists of a very simple 2d symbol. A line, a square, and a circle. The layer they are being moved to is set to be 'Not Visible'


    I selected them, and changed the layer attribute in the Object Info window.  It has been over 4 1/2 hours and it is till not finished processing the change.  


    I am Rundung VW 2019 SP2 on a 

    15", 2018 MacBook Pro

    2.9Ghz i9

    32 GB

    High Sierra 10.13.6


    With Process Manager, I can see the VW2019 process is running at %100, but the system CPU is 87% idle.  There is no load on the GPU.



    Spotlight sync is not enabled (I would hate to think how slow that would be)


    Is anyone else noticing slow handling of records?


    From the same file, I just performed the same operation on my old machine(15" 2012 MBPro, 2.6Ghz i7, 16Gig Ram, OSX 10.12.6), moving 1640 devices to a new layer.  It took over 45 minutes


  11. I am writing a script, and am having an issue with the GetWSSubrow functions.

    Here is a samble of the script, that creates a spreadsheet, and trys to get the number of subrows created.

    SSheet	:HANDLE;
    subrow	:INTEGER;
    SSheet := CreateWS('LXSymbols',2,4); {create worksheet with 2 rows and 4 columns}
    SetWSCellFormulaN(SSheet, 1, 0, 1, 0, '=DATABASE((R IN [''Lighting Device'']))');
    SetWSCellFormulaN(SSheet, 1, 1, 1, 1, '=(''Lighting Device''.''Symbol Name'')');
    SetWSColumnOperators(SSheet, 1,0,0,0,1,0,0); {Summarize Column 1}
    ShowWS(SSheet, TRUE);
    subrow := GetWSSubrowCount(SSheet, 1);
    Message('There are ',subrow, ' Lighting Symbols');

    I get an error online 14 saying that it expects a new factor. I get the same error regardless of which of the GetWSSubrow* functions I try.

    Am I doing something wrong, or is the function broken?

    Running VW2016 SP4 on Windows 10

  12. I would love to see a hot-key that could be used with the Number Instruments tool, where when the key is held, the number is not incremented.

    For example, when assigning circuit number to units, If there are 2 or 3 units on a circuit, it would be nice to be able to hold a key and assign the same value to multiple units, before progressing on to the next circuit.

    The same function could be utilized when assigning Circuit Name to multiple units manually.

  • Create New...