hexagon logo
Register Sign in
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 110 views
  • Users 0 members are here
Options
Related

unmark feature

whisho
I hope not to bother with my questions.
Sometimes they ask me to program certain features for a while. But usually not deleted and are staying and make the program longer. It currently takes about 1.5 hours. This time, I'm interested to know how to make a feature that is measured --X-- days, then unmark or delete and continue the program.
  • Easiest way is to make SETS, the use of MARKED SETS will pop-up a little window, in the window will be an icon for each different set, mark ALL the features you want for the set, then make the set, repeat for all variations of check points you want, then simply click on the set you want to check when you want to check it.
  • Sorry but I do not understand. Could you explain better? ... Thanks
  • I hope not to bother with my questions.
    Sometimes they ask me to program certain features for a while. But usually not deleted and are staying and make the program longer. It currently takes about 1.5 hours. This time, I'm interested to know how to make a feature that is measured --X-- days, then unmark or delete and continue the program.

    If I understand you correctly, it sounds like you want to create a feature that automatically unmarks itself after a set period of time. PC-DMIS doesn't have a built in function for that, but you could do it with some creative scripting.
    Personally I would suggest marking a calendar or if you use Microsoft Outlook setting a reminder then personally go in and delete it. It's not a good idea to keep adding features and then leaving them even after you no longer need them.
  • Schrocknroll. thanks so much for your comment..
    Ok. What I have today, is a counter and some variables that assigned the system date and the target date. With the command --if/goto--, valid measure and count this feature if the date is less than or equal to the target date and, if greater, makes a comment report that displays the times were measured from the date that program and, using a goto, jump to the next feature.

    I wanted unmark the feature automatically when the condition is met but, alternatively, could erase all the instructions --- including the feature. All this in a block---that I use for that purpose with any instructions or code?
  • Try to use SYSDATE, with an assignment and a calendar ! IF DATE=="10/10/2010" or "10/17/2010" (...) - block of prog - end if.
  • You can write it like this :
    ASSIGN\VAR1=SYSTEMDATE("MM'/'dd'/'yy") (be carefull : DD or YY doesn't works !)
    IF\VAR1=="10/04/10" OR "10/11/10"
    (prog to execute today or next week)
    END IF
  • I can only see two ways to go about this, you would need to create an outside script that would run and do this for you or you could try Jefman's if/then conditional. The problem with the if/then conditional is that you have to be very careful with what comes after the if/then. Things like alignments, rotations and reported features and maybe some others will not be ignored just because it skips the code if it doesn't meet the condition.

    Depending on how many different things you are trying to do here it may just be better to have seperate programs for the different features.
  • EHines is right, you should have to recall an alignment after end if.
    If you want to execute a part of program every monday (for example), you can as follow :
    ASSIGN\VAR1=SYSTIME()
    ASSIGN\VAR2=ELEMENT(1," ",VAR1)
    IF/VAR2=="Mon"
    (part of program)
    END IF
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement