Attention: Mapkey Syntax changed between DateCodes

Forum|Forum|11 years ago
June 16, 2014
2 replies
6236 views

I was upgrading from Creo 2.0 M090 to M110 and apparently the Syntax for some mapkeys has changed, Meaning they just stopped working.

Now for some mapkeys it's obvious when they do not work, but for others (like setting a parameter for example) these things can be easily overlooked.

I think it is very unprofessional to have such changes and not warn the users about this. Even worse, apparently there is not even a list with these changes...

I just have to find out for myself which mapkeys stopped working and then PTC will tell me what the difference is.

Which company makes design changes in its product without listing them, leaving the users without info and then tells them to test it themselves..

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.

Surfacing

J

JordyvanderVeld

1-Visitor

That sounds very troublesome indeed! Could you re-record the mapkey and post the new and old config.pro so the two could be compared?

P

ptc-4392950

Author

1-Visitor

That is indeed what i did to figure out why a mapkey stopped working. But when having over 50 mapkeys it's quite a job do check them all. Especially when paying that much Support

for example look at this command

~ Select `pagesetup` `TblFormats` 2 `1` `fmt`;

it has changed to

~ Select `pagesetup` `TblFormats` 2 `0` `fmt`;

It's not up to the user to spot this, but up to PTC to have a list of these changes.

J

JordyvanderVeld

1-Visitor

I get what you're saying. I spent the last 15 minutes googling for differences between builds and I haven't found anything so far.

On the other hand, M110 has been released exactly one month ago. I wonder why no-one else hasn't noticed this yet...

But I agree, it's a must to notify gamebreaking changes.

M

Mahesh_Sharma

22-Sapphire I

Arno,

This change in mapkey is due to a fix submitted for a serious bug for format replacement in multi-sheet drawings. Earlier mapkeys were not affecting the users for single sheet drawings, but for multisheet drawing users it was a serious bug as it was recording the sheet number. In earlier datecodes if you are working with multisheet drawing, mapkey will record the sheet number, hence when user will try to run mapkey on other sheet, format on that sheet will not update and instead of that it will again update the format for which it was recorded.

To correct this behaviour, fix was submitted and that to not to record the sheet number.

As you mentioned:

Earlier mapkey was

~ Select `pagesetup` `TblFormats` 2 `1` `fmt`;

it has changed to

~ Select `pagesetup` `TblFormats` 2 `0` `fmt`;

here 1 was the sheet number and now it is 0 which is not for any specific sheet.

Hence, new mapkeys will work with multisheet drawings and will not change the format only in a specific sheet.

I hope this will clarify the issue in detail.