Jump to content

Sam Jones

Member
  • Posts

    854
  • Joined

  • Last visited

Reputation

305 Spectacular

10 Followers

Personal Information

  • Occupation
    Technical Director
  • Homepage
    www.autoplotvw.com
  • Location
    Los Angeles

Contact Info

  • Skype
    AutoPlotVW

Recent Profile Visitors

6,071 profile views
  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.
  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. The objects are rarely overlapping, but, on ocasion, they wiil. As to relative and absolute stacking order, how would I get either?
  6. 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.
  7. The new doppelganger objects are drawn all on one other layer, different from the selected objects and at a different scale.
  8. 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.
  9. Pat, I don't think this works with stacking reordered by the user, but i need to make a test file and isolate the issue. @klinzeyHow do I convert a handle to a string.
  10. If I get the layer of an object, how do I know if the layer it is on stacks above or below a layer another object is on?
  11. 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??
  12. 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.
  13. 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.
×
×
  • Create New...