hexagon logo
Register Sign in
  • Replies 10 replies
  • Subscribers 225 subscribers
  • Views 108 views
  • Users 0 members are here
Options
Related

Multiple Selection Option - Using Forms

mattfurtaw
Okay GURU's. I am looking for the easiest way to have the operator select multiple items at the beginning of the program in order to inspect certain features. We have a part with 18 different features and instead of running the entire program for 1 feature that was adjusted I would like to prompt the question "Which blocks would you like to check....1, 2, 3, 4..etc " and so on.

I don't have much expierence in this area and I know that you can use VB but with my skills I am not getting it. Any help would be apprieciated.
Parents
  • Marked sets would handle that but you could have an infinite number of combinations from the sounds of it if you want to check more than 1.

    One way that occurs to me is to use YES/NO inputs and CHECK commands.
    c1: do you want to check feature #1 (yes/no)
    c2: do you want to check feature #2 (yes/no)
    etc.
    on the executable side, evaluate each comment before the feature.

    before feature 1, check the c1.input.
    If YES, it runs the feature.
    If NO, it skips to the next feature.

    continue for all features.

    the problem I foresee with this though is report commands tend to ignore logic statements. EX: you may have skipped over feature #5 but feature #5 will get reported anyway if you have a DIM command for it.
    Don't know how to get around that yet (unless using marksets)

    I don't know about the VB scripting, I've never gotten into that.
Reply
  • Marked sets would handle that but you could have an infinite number of combinations from the sounds of it if you want to check more than 1.

    One way that occurs to me is to use YES/NO inputs and CHECK commands.
    c1: do you want to check feature #1 (yes/no)
    c2: do you want to check feature #2 (yes/no)
    etc.
    on the executable side, evaluate each comment before the feature.

    before feature 1, check the c1.input.
    If YES, it runs the feature.
    If NO, it skips to the next feature.

    continue for all features.

    the problem I foresee with this though is report commands tend to ignore logic statements. EX: you may have skipped over feature #5 but feature #5 will get reported anyway if you have a DIM command for it.
    Don't know how to get around that yet (unless using marksets)

    I don't know about the VB scripting, I've never gotten into that.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement