delete the mapkey from config.pro but when import it again came back?

[mgupta-4]

Dear All,

I made a config.pro file it has so many mapkeys but one of the key i made like " 1 " for plane on/off ,now i want to delete it from my config.pro .

but everytime when i delete it came again .

i checked the notepad file to delete from there but there that mapkey not found

Please help what to do?

Thanks

Manish

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.

[dschenken]

PTC reads multiple files to load options, such as mapkeys. You may have removed it from one config.pro, but not from other locations. There are several config.pro files in different locations.

Open the Options. There is a view that says Current Session. This should be the top of a drop down that lists all the files that are the source of current options. Change from one to the next until you see the mapkey you are interested in, which will tell which file you need to edit.

To make things easier, create a separate file called mapkey.txt. Then move all the mapkey definitions to that file. Finally create a mapkey that loads opens the options using mapkey.txt and store it in config.pro. Any new mapkeys can be saved in mapkey.txt; PTC appends the mapkey definitions to the file.

[mgupta-4]

Dear David,

this seems interesting ,can you please elaborate the process that how to create a mapkey that loads the mapkey.txt (all mapkeys txt file) and store it in the config.pro.

Please help.

Thanks,

Manish Gupta

[dschenken]

Record a mapkey that opens the Options

From the Options, open the file you want to store the mapkeys in.

Change the file type to all and select and open the text file with the mapkeys in it.

Close the Options.

Stop recording and save the changed mapkey into the config.pro file.

Once the mapkeys are in a .txt file, they are easier to manage as they don't clutter the rest of the config options. Being separated one can also edit them without Windows trying to start a Pro/E session.

I typically named the files as mapkey_functions.txt where functions are what the mapkey did or the

You can also include comment lines in the mapkey files using the "!" character in the first position on the line.This is a good practice to leave reminders of what the mapkey does if it isn't very obvious. It is easy to forget.

Here's some info for Creo 3, http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/whats_new_pma/whats_new_pma-rds.02.095.html

Typical mapkey entry, this is only two lines; web page breaks it. Line labels are not part of the mapkey:

(line A) mapkey $F10 @MAPKEY_NAMEChanges to Next Drawing Sheet;@MAPKEY_LABELSheet Next;\

(line B) mapkey(continued) #sheets;#set current;

Disassembled mapkey:

1) mapkey

2) $F10

3) @MAPKEY_NAMEChanges to Next Drawing Sheet;

4) @MAPKEY_LABELSheet Next;

5) \

6) mapkey(continued)

7) #sheets;

😎 #set current;

1) tells PTC that this is a mapkey config option

2) Key sequence, in this case it is short for the F10 Function key. Without $ it would require typing F 1 0

3) Mapkey name to remind the user what the mapkey does, ends with ";" (semicolon)

4) Mapkey label is another reminder, ends with ";" (semicolon)

5) Continuation character "\" appears at the end of the line

6) tells PTC that this is a continued mapkey

7) PTC command, ends with ";" (semicolon)

😎 Another PTC command, ends with ";" (semicolon)