Skip to main content
12-Amethyst
Oct 29, 2015 9:33 AM UTC
Solved

Creo 3.0 mapkey/ribbon issues

We recently upgraded to creo 3.0 m060 from creo 2.0.

One problem we are facing is that some mapkeys added to the ribbon stopped working.

The mapkeys work if we type the text on the keyboard, but adding them to the ribbon nothing happens. The buttons don´t do anything.

What the mapkeys do is open a config file and open a file.

This only happens in two computers. The others works fine.


Anyone experienced this?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
12-Amethyst
Nov 3, 2015 7:34 PM UTC

Rebuilding a new ribbon from the scratch in Creo 3 has solved the problem.

10 replies

12-Amethyst
Oct 29, 2015 11:42 AM UTC

Jose,

This is such an open question because we have no knowledge of your set-up configurations so with what little was offered, I suggest to see if the two computers share the exact same .ui and .pro files as the other ones that do work. Make sure that any local/user created .ui and .pro files are nullified.

ron

Translate
12-Amethyst
Oct 29, 2015 11:49 AM UTC

Sorry, I forgot to mention that all the computers use the same .ui and .pro files.

Translate
24-Ruby III
Oct 29, 2015 11:56 AM UTC

Jose,

can you publish problematic mapkeys ?

MH

Translate
12-Amethyst
Oct 29, 2015 12:12 PM UTC

Sure,

See attached files.

Mold.pro is a configuration file loaded by the mapkeys.

Translate
24-Ruby III
Oct 29, 2015 1:13 PM UTC

Jose,

I opened problematic_mapkeys.pro and found these mapkeys:

lingua

lingua1

lingua2

omfg

Note 1

I think that user is not able to launch lingua1 or lingua2. Creo can launch lingua, only. Suggestion: rename lingua to lingua0.

Note 2

mold.pro must be present in current working directory. Is this rule fulfilled ?

Note 3

mold.pro when edited improperly can get double extension mold.pro.txt. Such file can be seen in Windows Explorer as mold.pro. This can cause confision.

Note 4

I can test your files later.

MH

Translate
Jose_Costa12-AmethystAuthorAnswer
12-Amethyst
Nov 3, 2015 7:34 PM UTC

Rebuilding a new ribbon from the scratch in Creo 3 has solved the problem.

Translate