Jump to content

PMGuide - Mouse and Keyboard Input: Difference between revisions

From EDM2
Line 2: Line 2:


==About Mouse and Keyboard Input==
==About Mouse and Keyboard Input==
        System Message Queue
===System Message Queue===
        Window Activation
===Window Activation===
        Keyboard Focus
===Keyboard Focus===
        Keyboard Messages
===Keyboard Messages===
            Message Flags
====Message Flags====
            Key-Down or Key-Up Events
====Key-Down or Key-Up Events====
            Repeat-Count Events
====Repeat-Count Events====
            Character Codes
====Character Codes====
            Virtual-Key Codes
====Virtual-Key Codes====
            Scan Codes
====Scan Codes====
            Accelerator-Table Entries  
====Accelerator-Table Entries ====
        Mouse Messages
===Mouse Messages===
        Capturing Mouse Input
===Capturing Mouse Input===
            Button Clicks
====Button Clicks====
            Mouse Movement  
====Mouse Movement====
 
==Using the Mouse and Keyboard==
==Using the Mouse and Keyboard==
===Determining the Active Status of a Frame Window===
===Determining the Active Status of a Frame Window===

Revision as of 03:52, 29 April 2025

An OS/2 Presentation Manager application can accept input from both a mouse (or other pointing device) and the keyboard. This chapter explains how these input events should be received and processed.

About Mouse and Keyboard Input

System Message Queue

Window Activation

Keyboard Focus

Keyboard Messages

Message Flags

Key-Down or Key-Up Events

Repeat-Count Events

Character Codes

Virtual-Key Codes

Scan Codes

Accelerator-Table Entries

Mouse Messages

Capturing Mouse Input

Button Clicks

Mouse Movement

Using the Mouse and Keyboard

Determining the Active Status of a Frame Window

Checking for a Key-Up or Key-Down Event

Responding to a Character Message

Handling Virtual-Key Codes

Handling a Scan Code