DOCUMENT:Q104789  09-JUN-1999  [win16sdk]
TITLE   :DOC: WM_TIMER Case on Page 94 of Guide to Programming
PRODUCT :Microsoft Windows Software Development Kit
PROD/VER:WINDOWS:3.1
OPER/SYS:
KEYWORDS:kbdocfix kb16bitonly kbSDKPlatform kbWndw kbWndwMsg

======================================================================
3.10
WINDOWS
kbprg kbdocerr

-------------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows Software Development Kit (SDK) 3.1 
-------------------------------------------------------------------------------

SUMMARY
=======

Section 4.2.13, page 94, of the Windows SDK "Guide to Programming" manual shows
how to add WM_TIMER processing to a window procedure. The code in the book is
actually WM_LBUTTONDBLCLK. This is an error.

Chapter 4 of the "Guide to Programming" manual builds a sample program called
input. The correct WM_TIMER case is found within INPUT.C, which is in the
\GUIDE\INPUT directory of the Windows SDK directory. If this is a Visual C++
installation, INPUT.C will be in the \SAMPLES\INPUT directory.

The correct code is listed below:

      case WM_TIMER:

         wsprintf(TimerText, "WM_TIMER: %d seconds", nTimerCount += 5);
         InvalidateRect(hWnd, &rectTimer, TRUE);
         break;

Additional query words: 3.10

======================================================================
Keywords          : kbdocfix kb16bitonly kbSDKPlatform kbWndw kbWndwMsg 
Technology        : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK310
Version           : WINDOWS:3.1

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1999.