Added mapkeys not showing in Ribbon - Creo 1.0-m030

[davehaigh]

I have three mapkeys I'm trying to add to the ribbon and they don't show up. Other mapkeys show up no problem.

If I create a new cascade. The cascade shows up in the ribbon.

[cid:image004.jpg@01CD083E.1FE83A80]

As soon as I add one of these mapkeys to the cascade, it disappears.

[cid:image006.jpg@01CD083E.1FE83A80]

If I add a different mapkey to the cascade, it shows up.

[cid:image009.jpg@01CD083E.1FE83A80]

Any ideas? The mapkey works if I type the key name.

The problem mapkeys are loading a config file to change the config option cleanup_drawing_dependencies.

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550


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.

[davehaigh]

I have a workaround for the SPR.

Thanks to Olaf Corten, pointing out to me that the forward slash in the key name was the cause of the problem in the ribbon. The mapkey works when typed from the keyboard but you can't add it to the ribbon if it has a slash in the key name. The other thing he pointed out, that really helps with Creo, is you want to use cmdmgr_trail_output yes in your config.pro

I've also been playing around with where Creo stores the customizations to the ribbon. There are three possible locations. Creo will read all three.

1. The Creo loadpoint <--File has to be renamed

2. The Creo Cache <--The default location

3. The Startup Directory <--Requires a config option

By default the ribbon customizations are stored in a .ui file with this name:
creo_parametric_customization.ui

The Creo Cache Location

[ChrisCollinson]

David,

Thanks for taking the time to summarise this little gotcha, I've been
trying to get this to work for a little while now and with this doc have
managed to do what I need, so thank you for this




Best Regards

Chris Collinson
CAD Administrator