Maps keys CREO2, why don't "p" and "o" work?

Forum|Forum|13 years ago
August 17, 2012
3 replies
7374 views

First time poster, long time proe user...

Finally updated all my map keys in creo 2, well, so I thought but noticed that any map key starting with a "p" or "o" don''t work. They work if you manually run the map key in the Map Key dialogue but not out of it?... Anyone notice this or have a reason for it/solution or should I just relabel them?

Best answer by ptc-2053410

I did get it work, I think it had something to do with a mapkey that works in wildfire 5 for changing to a previous view which was “P” and that conflicted with the mapkeys associated with the ribbon mapkeys (which you should be able to turn off and or edit yourself, in fact I would like to see my own map keys up there the whole time). Once I deleted that key it worked fine

M

MartinHanak

24-Ruby III

Paul,

in my installation of Creo Parametric 2.0 M010 I defined two mapkeys - oo and pp and they work well. I guess the problem is hidden inside your config.pro file. You have to check names of your mapkeys. Eq. mapkeys must not have names p, pp, ppp, ... Correct naming convention is p1, p2, p3, ...

Martin Hanak

Patriot_1776

22-Sapphire II

Dunno about that Martin, I have a mapkey that is: "pnt". The problem is that unlike AutoCAD, where the "mapkeys" are activated by a return, in Pro/E they are activated the moment the neccessary keys are entered.

If you have 2 mapkeys, one loaded in the config.pro at the system level and one user-specific as follows:

pn

pnt

The "pn" will always work and the "pnt" will get you the "pn" function because you never get to strike the "t" key. This is an area where AutoCAD's "mapkeys" (called "aliases" in A/C) work better because they give you a lot more flexibility. Most of my mapkeys in fact came from my many years on A/C/

J

James62

1-Visitor

The "pn" will always work and the "pnt" will get you the "pn" function because you never get to strike the "t" key. This is an area where AutoCAD's "mapkeys" (called "aliases" in A/C) work better because they give you a lot more flexibility. Most of my mapkeys in fact came from my many years on A/C/

This is what makes Creo/Pro/E so unproductive in compartison with AutoCAD. Because when making a typo during typing of a mapkey the command line gets stuck until everything gets deleted with delete key. In AutoCAD you can just hit RMB to get invalid command in case of making a typo and start typing in the macro again.

B

BrianMartin

13-Aquamarine

Hi Paul...

Did you ever get these to work? I haven't had a problem with mapkeys in Creo 2. What Martin Hanak was saying was that perhaps you had a problem in the mapkey definition or you may have had a duplicate mapkey using the "p" or "o" letters. Did you check these?

Thanks!

-Brian

P

ptc-2053410

AuthorAnswer

1-Visitor

I did get it work, I think it had something to do with a mapkey that works in wildfire 5 for changing to a previous view which was “P” and that conflicted with the mapkeys associated with the ribbon mapkeys (which you should be able to turn off and or edit yourself, in fact I would like to see my own map keys up there the whole time). Once I deleted that key it worked fine