Ignore:
Timestamp:
Oct 26, 2001, 12:04:13 PM (24 years ago)
Author:
phaller
Message:

.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/user32/oslibmsg.cpp

    r7211 r7212  
    1 /* $Id: oslibmsg.cpp,v 1.47 2001-10-26 09:10:12 phaller Exp $ */
     1/* $Id: oslibmsg.cpp,v 1.48 2001-10-26 10:03:34 phaller Exp $ */
    22/*
    33 * Window message translation functions for OS/2
     
    248248        // if this is a keyup or keydown message, we've got to
    249249        // call the keyboard hook here
    250         if(pMsg->message <= WINWM_KEYLAST && pMsg->message >= WINWM_KEYDOWN)
     250        // send keyboard messages to the registered hooks
     251        switch (pMsg->message)
    251252        {
    252           ProcessKbdHook(pMsg, TRUE);
     253          case WINWM_KEYDOWN:
     254          case WINWM_KEYUP:
     255          case WINWM_SYSKEYDOWN:
     256          case WINWM_SYSKEYUP:
     257            // only supposed to be called upon WM_KEYDOWN
     258            // and WM_KEYUP according to docs.
     259            if(ProcessKbdHook(pMsg, TRUE))
     260              goto continuegetmsg;
     261            break;
    253262        }
    254263   
     
    300309 
    301310  // send keyboard messages to the registered hooks
    302   if(pMsg->message <= WINWM_KEYLAST && pMsg->message >= WINWM_KEYDOWN)
     311  switch (pMsg->message)
    303312  {
    304     // only supposed to be called upon WM_KEYDOWN
    305     // and WM_KEYUP according to docs.
    306     if(ProcessKbdHook(pMsg, TRUE))
    307       goto continuegetmsg;
    308   }
     313    case WINWM_KEYDOWN:
     314    case WINWM_KEYUP:
     315    case WINWM_SYSKEYDOWN:
     316    case WINWM_SYSKEYUP:
     317      // only supposed to be called upon WM_KEYDOWN
     318      // and WM_KEYUP according to docs.
     319      if(ProcessKbdHook(pMsg, TRUE))
     320        goto continuegetmsg;
     321      break;
     322  }
     323 
    309324  return rc;
    310325}
     
    374389        // if this is a keyup or keydown message, we've got to
    375390        // call the keyboard hook here
    376         if(pMsg->message <= WINWM_KEYLAST && pMsg->message >= WINWM_KEYDOWN)
     391        // send keyboard messages to the registered hooks
     392        switch (pMsg->message)
    377393        {
    378           ProcessKbdHook(pMsg, fRemove);
    379         }
     394          case WINWM_KEYDOWN:
     395          case WINWM_KEYUP:
     396          case WINWM_SYSKEYDOWN:
     397          case WINWM_SYSKEYUP:
     398            // only supposed to be called upon WM_KEYDOWN
     399            // and WM_KEYUP according to docs.
     400            if(ProcessKbdHook(pMsg, fRemove))
     401              goto continuepeekmsg;
     402            break;
     403        }
     404   
    380405        return TRUE;
    381406  }
     
    419444
    420445  // send keyboard messages to the registered hooks
    421   if(pMsg->message <= WINWM_KEYLAST && pMsg->message >= WINWM_KEYDOWN)
     446  switch (pMsg->message)
    422447  {
    423     // only supposed to be called upon WM_KEYDOWN
    424     // and WM_KEYUP according to docs.
    425     if(ProcessKbdHook(pMsg, fRemove))
    426       goto continuepeekmsg;
     448    case WINWM_KEYDOWN:
     449    case WINWM_KEYUP:
     450    case WINWM_SYSKEYDOWN:
     451    case WINWM_SYSKEYUP:
     452      // only supposed to be called upon WM_KEYDOWN
     453      // and WM_KEYUP according to docs.
     454      if(ProcessKbdHook(pMsg, fRemove))
     455        goto continuepeekmsg;
     456      break;
    427457  }
    428458
Note: See TracChangeset for help on using the changeset viewer.