Project

General

Profile

Bug #2432

investigate and fix collisions related to event/key codes reported by KEY-CODE and LAST-EVENT

Added by Constantin Asofiei over 11 years ago. Updated over 11 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to User Interface - Feature #2423: add proper key-to-event mappings in GUI Closed 06/08/2015

History

#1 Updated by Constantin Asofiei over 11 years ago

From #2423 note 7:

Another frustrating fact about events: although the WINDOW-* events are reporting LAST-EVENT:CODE values (other than -1), these values are not reported by the KEY-CODE("WINDOW-*") function: this always returns -1... Progress either uses different tables for PROGRESS and KEYPRESS events or something else is happening. The collisions are (for GUI WINDOW-* events):
  1. WINDOW-CLOSE: 1078 - ALT-6
  2. WINDOW-MAXIMIZED: 1094 - ALT-F
  3. WINDOW-MINIMIZED: 1095 - ALT-G
  4. WINDOW-RESTORED: 1096 - ALT-H
  5. WINDOW-RESIZED: 1120 - ALT-`

Investigation is needed to identify why this collision appears, and fix as necessary.

Also available in: Atom PDF