Repeatable Mapkey Generator - How to loop Creo Mapkey

@VladimirPalffy Awesome utility! You can trim the mapkey code as several of the lines aren't needed:

mapkey rm @MAPKEY_NAMEGenerates custom Creo Mapkey;@MAPKEY_LABELRepeatable Mapkey;\
mapkey(continued) ~ Command `ProCmdModelOpen`;\
mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\
mapkey(continued) ~ Input `file_open` `Inputname` `TEST.PRT`;\
mapkey(continued) ~ Update `file_open` `Inputname` `TEST.PRT`;\
mapkey(continued) ~ Activate `file_open` `Inputname`;\
mapkey(continued) ~ Activate `out_of_date_annots` `psh_continue`;\
mapkey(continued) ~ Activate `storage_conflicts` `OK_PushButton`;%4k;

Some other ideas/suggestions:

• Automatically clicking ok to PDM storage conflicts (~ Activate `storage_conflicts` `OK_PushButton`;) could be risky. In the current state, the user could set the config option dm_checkout_on_the_fly to handle this. Could add a note on the webpage about this setting or maybe add some PDM options to 'check out' or 'continue' for all conflicts? Maybe it's simplest to just mention the setting.
  • Code for 'Continue':
    • ~ Activate `storage_conflicts` `Resol3`;\
      ~ Activate `storage_conflicts` `OK_PushButton`;\
  • Code for Check out:
    • ~ Activate `storage_conflicts` `Resol1`;\
      ~ Activate `storage_conflicts` `OK_PushButton`;\
• Could add an text input option to the webpage about what mapkey(s) to run instead of being hardcoded to %4k.
• Could add an option to add the close window command after running the mapkey(s): ~ Command `ProCmdWinCloseGroup`;\
• Cleanup of the input list of parts if there's multiples of the same file  - test.prt.1 and test.prt.2

Nice work!