PF> DS> When scrolling through text, using the arrow keys, my program falls
  > DS> behind the input buffer, causing the annoying effect of scrolling after
  > DS> the key has been released.

PF> DS> The vertical scroll buttons don't have this problem.

PF> DS> I thought that the SB msgs may have been combined by OS2, so I used
  > DS> WinPostMsg for the vertical arrow keys, to use the SB vertical logic.

PF>Are you drawing for each scroll?  Don't.  Instead,  make sure you are NOT
  >using a "CS_SYNCPAINT" window,  and scroll & invalidate
  >(WinScrollWindow/WinInvalidateRect) the window.   PM will
  >be smart enough to skip any WM_PAINT's that are no longer
  >valid.

PF>Using thie technique, you can even smooth scroll a bitmap.

Okay, I will check out your suggestions.  However, I still don't
understand why the SB messages do not cause scrolling.  Is it as I
suspected that OS/2 was combining them into one message?

Last night I expanded the experimentation by using the WinPostMsg, but I
created my own messages (WM_USER_VK_DOWN, etc) hoping that OS/2
would combine multiple messages into one ... no luck.  I then tried to
*drain* the message queue of a particular message, for instance
WM_USER_VK_DOWN, using WinPeekMsg w/ PM_REMOVE, but that did not work
either.

Thanks for the response above.
___
 X OLX 1.53 X Gravity isn't my fault!  I voted for velcro.

--- Maximus/2 3.00