Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    11
  • Views views
    381
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to see current state of keystroke table

RobertRedekop

Hi everyone.  Our application does dynamic changes to the KEYSTROKE variable settings for various keys.   Due to some recent odd behavior I was wondering if there was a way to get the current state of the KEYSTROKE settings?

All I have figured out is that when using the debugger, changes to the environment get recorded in the error log file.  That turned out to be enough, but the original question still stands.  I figure I could write a utility to read through the trace file and sort by the key code, to see what the current state of the settings are, but I'll leave that until it's needed.  If anyone knows a better way, I would love to hear it.

  • 0  

    The KEYSTROKE variable cannot be read with the ACCEPT FROM ENVIRONMENT statement so you cannot query the current table of keys. Perhaps when you modify the KEYSTROKE in your program you can write to a log file specific for this purpose. That way it will be easier to parse and query that log when you need to without having to filter out all other unnecessary information. 

    ---

    Martin Turner

    Senior Technical Support Engineer

    Rocket Software

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.