Skip to main content
tbraxton
22-Sapphire II
tbraxton22-Sapphire II
22-Sapphire II
June 2, 2024
Question

Mapkey toggle scheme no longer works in Creo 11+

  • June 2, 2024
  • 2 replies
  • 1876 views

Creo 11+ toggle mapkey schemes that call config.pro files on the fly from within the mapkeys no longer work. This was to be expected with the introduction of the mapkey.pro file to define mapkeys, however I am not able to record a mapkey that will load a mapkey.pro file on the fly thereby rendering the toggle strategy dead.

 

Has anyone been able to update a toggle type mapkey to work in Creo 11 yet. I would be interested to see how you are loading mapkey.pro files on the fly using a mapkey.

 

I am still able to load config.pro files on the fly using a mapkey in tests but no luck with the mapkey.pro files.

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
June 3, 2024

Hi,

my solution is little bit tricky.

1.] I have trail file which loads file containing mapkeys ... the file is attached

2.] I have mapkey which runs the above mentioned trail file ... the file is attached

 

In https://community.ptc.com/t5/Customization/Creo11-and-Mapkey-pro/m-p/949207 discussion I published information how to load mapkeys during Creo start.

    tbraxton
    22-Sapphire II
    tbraxton22-Sapphire IIAuthor
    22-Sapphire II
    June 27, 2024

    PTC support has confirmed today that it is not possible to load mapkey.pro on the fly and a high severity SPR has been assigned to the issue. I will update this post when a solution is implemented.

      tbraxton
      22-Sapphire II
      tbraxton22-Sapphire IIAuthor
      22-Sapphire II
      November 20, 2024

      R&D has an example of a workaround, I am waiting to get it and test it to see if it resolves the issue. The SPR is closed. I will add information here once I get a chance to test the proposed solution.

       

      The stated resolution from PTC is: Mapkeys can be loaded/Imported from File > Options > Mapkeys Settings

       

      tbraxton_1-1732123725378.png

       

       

      Terms & ConditionsAccessibility statement