Jump to content

Sam Jones

Member
  • Posts

    854
  • Joined

  • Last visited

Posts posted by Sam Jones

  1. Is it possible to capture if a modifier key was pressed during the drawing of a line that is being used by a path object (drawing a cable)?  If so, how?  If not is there some way to capture an action during the creation of a path object that will modify the processing of the path object?

  2. Cookie,  your designer does not have the Lighting Device (LD) PIO loaded into his VW.  PIOs are loaded when VW starts up.  When he opens your drawing, LD objects will show up and LDs can be counted, but only as Lighting Devices.  When he selects an LD it will display all the values but they cannot be changed or manipulated.  Not only that, but since the LD code is not present, the LD cannot perform any of its functionality, like focusing, displaying beams, interacting with the Label Legend.  Bottom line,  he, or both of you are hosed.  Sorry.

  3. Well, Pat, you were right.  FInLayer and FSObject yield the bottom of the stacking order.  One needs to be sure there is not another routine sorting the object list, which was the case in the original application.  My bad.  It should be obvious that collecting objects should be by layer and then by the order in the layer, but it is hard to imagine that would not be the case whenever collecting objects across layers.  Maybe if a collection criteria dealt with classes as the main criteria the visibility stacking could be compromised.  For the moment, i don't care about that scenario.  Pat and Raymond, thanks.

    • Like 2
  4. I don't think FInLayer and FSObject(LayerHand) will yield the correct stacking order.  They don't seem to in the original application (PIO).  They seem to consistently yield creation order, but there is so much going on that file that I need to create a special limited file to test known stacking order against info yielded by vs functions

  5. 47 minutes ago, Pat Stanford said:

    Start at bottom layer and work up through stacking order.

    How do I know what the stacking order is?  If I don't need to know what it is, how do I work up through it?

    I need to make a list of selected symbols, in order to place the dopplegangers.  I can then sort the list on any criteria I know about or collect.  Theoretically, that would first be by layer order, and then by stacking order.  Getting the stacking order is the trick.  My preliminary investigations indicate that the handles to the objects do not provide a reliable stacking order, but I am refining my test file and the code to test indications of stacking order.

  6. I want to collect the handles of all the selected editable objects and then place different symbols based on what the selected objects are.  I don't want to replace the original selected objects.  I just want to place other different symbols (dopplegangers) down in the same stacking order as the stacking order of the original selected symbols.  That way the dopplegangers obscure (or not) each other in exactly the same way as the original objects obscure (or not) each other.

  7. Is there a way to retrieve the stacking order (may be relative) of objects in a layer, and is there a way to retrieve the stacking order (number?) of a layer?

    I want to create some objects based on the visual stacking order of other selected objects.  "FSActLayer" and "FSObject" will retrieve object handles in their creation order, and that would yield their stacking order, except when the stacking order is changed by the user.  Additionally, I would need to know the relative stacking order of the layers the selected objects are in, because that would change their visible stacking order in the drawing from their creation order.

    Too much to ask??

  8. Pat is pointing at the correct parameter, but that is a list of alternate names.  If you are needing to reference the hoist origin in a formula or are just typing in field names into the database header you will need to use the universal name "OriginName".  Typically the formula at the top of the column of hoist origin names is ='BrxHoist'.'OriginName'.  You will need to use 'BrxHoist'.'OriginName' in any worksheet formulas that reference that parameter.

     

     

    • Like 2
  9. BTW,  It is tempting to use the record "Truss Record" as a criteria in order to pick up symbols.  However, you cannot use "Truss Record" as a criteria in a drawing that has "TrussItem" objects (items inserted with the Truss Insertion tool).  "Truss Item objects have 2 versions of the "Truss Record" attached to them; doubling the number of actual truss pieces.

     

    • Like 2
  10. Change the database criteria in Mark's worksheet to =DATABASE(INVIEWPORT & INOBJECT & INSYMBOL & (PON='TrussItem')).  This will allow you to count TrussItems in Hanging Positions as well.

    Additionally, the above criteria will only count truss pieces inserted with the Truss insertion tool.  Truss symbols placed in the document as symbols will not be counted with this criteria specification.

    HTH.

  11. 3 hours ago, Jesse Cogswell said:

    Unfortunately, none of the other data seems to come through (scale, elevation, transparency, etc), so that would have to be manually configured in the script.

     

    So it would seem that that would mean using the text file approach is the only way to copy scale, elevation, transparency, etc into another file.

  12. It would be interesting to get a list of object types that can be touched with the BuildResourceList() procedure.  It would be very strange if the object type "21" (polyline) was able to be imported.  Would that import every polyline in the document?  What would the index number even mean?  So...  Maybe all the "...definition" objects can be touched, but that would leave out "Layer", object type "31".  What about Viewports, object type "122"

    Is there a list or can a list be made of all the objects the  BuildResourceList() procedure can see and then be imported by the ImportResourceToCurrentFile() procedure?

  13. 4 minutes ago, Pat Stanford said:

    Or, maybe .... A script that would create a worksheet of the items to be restored. Which could then be imported and used to recreate.  That might work.

     

    And that might work for you also and avoid the txt file

     

    For you, the worksheet seems like a good solution, but the layer and class dialogs do what I need.  The esoteric workflows I mentioned revolve around sharing the created text files in a work group situation.  Not a lot different from just sharing .vwx files and using the layer and class dialogs, just a little less clicking and a little less file size intensive.  And some of my users are just familiar with them.  Familiarity, trumps a lot of "workflow stuff".

  14. Josh,  I hope you highlight BeamViz and ProjectionViz at your NY Spotlight User Group presentation.  Awesome tools, Awesome 3rd party engineering.  They work the way I need them to work.  Although I really appreciate the accomplishment that is ProjectionViz, I don't have a lot of use for its power.  BeamViz does everything I need to visualize the fixtures in the plot.

    • Like 4
  15. 2 hours ago, Pat Stanford said:

    You can Import Layers/Classes from the Organization

     

    I never noticed the "choose..." button in those dialogs.  That's handier.  There are some layer and class sharing workflows that will prefer working with the text files, but they are pretty esoteric.  What is the workflow you envisage that would want a script to query another file not using the layer and class dialogs?

  16. Nope.  I had to make commands that would export file and class names and their attributes to a text file, and commands that would read those text files creating the layers and classes in the active file from which the import commands were run.  The scheme works well, but it would be nifty to bypass the export and just read layer and class info from another file.  I think you can only read resources from another file, and classes and layers are not resources.  If one of the others knows something that I don't that would be great.

     

×
×
  • Create New...