|
I am currently using a lot of the ENPTUI controls like MOUBTN, PSHBTNFLD, SNGCHCFLD.
It seems that double clicking on the screen with the mouse emulates an ENTER key event if MOUBTN is not defined in the DDS. I would prefer to capture the double click event and ignore it if possible. It could be just a configuration issue, but I would prefer this to work whether the user's workstation is configured to treat Left mouse button double click as an enter key or not. So I added MOUBTN(*ULD E00) to my display file which traps the double click and returns it as an event to the program. I can retrieve the event by interrogating the AIB byte in the display feedback area. Documentation says that valid event codes are E00 - E15, and since there is no documentation (that I can find which links these event codes to AIB values, I tried them all, just to see what I would get back. E00 - E09 return x'70' - x'79', but E10 - E15 report 'Function key not allowed' on the Status line, and the Keyboard is locked.
Does anyone know why E10-E15 behave differently than E00-E09?
Is there any documentation on these display file events other than in the DDS manual in the MOUBTN section?
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.