Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
==-==-==-Internet Email Confidentiality Footer-==-==-==
Privileged, Proprietary, or Private information may be contained in this message. If you are not the intended addressee or responsible for the delivery of this message to the intended addressee, you are not authorized to possess or copy this message or its contents without the authorized consent of an UnderSea Sensor Systems, Inc. (USSI) representative. In such a case, you should destroy this message and notify us immediately. Opinions, statements, and other information expressed in this message are not published or endorsed by USSI unless otherwise indicated by an authorized representative independent of this message.
Terry wrote
Hi Dustin & John,
We are skipping WF5, so I can't test it right now, but you might try the following to see if it will tell you what is happening.
Record a new mapkey, and during that operation, execute an existing mapkey (e.g., by keyboard shortcut), and then save the
recorded mapkey. Then open it up in a text editor, and see how it shows the portion where you executed the existing mapkey.
(Is it doing something different that putting a % in front of it?)
Regards,
Terry
I had tried this before, but pushing the F# buttons do not accomplish anything during the record and doesn't show in the resultant code. I then considered using command buttons to define the mapkey with record. Turns out that this does work, and generates this line for the mapkey: $F5 ~ Activate `main_dlg_cur` `$F2.dtDtmD`;;~ Activate `main_dlg_cur` `$F4.dtDtmD`;
This mapkey F5 only runs 2 other mapkeys (F2 and F4). I think one would need to have the commands in your control panel for this to work, but it does legitimize the mapkey.