🚀 go-pugleaf

In article <1auvr1INNjg0@falcon.natinst.com> uma@natinst.com (Uma Arunkumar) writes:
>****************** PM QUESTION in OS2 2.0************************
>I am a beginner in PM programming in OS/2 2.0. 
>
>
>I am just trying to create a child window.  
>I have created a main window with frame, sysmenu, scroll bar, 
>minimize maximize buttons etc using WinCreateStdWindow.  
>This window displays the company logo and product information.
>I have used some simple graphics functions.  
>As soon as the user hits any key, the next screen should be displayed.
>
>The questions are given below:
>(i) Do I have to create a child window or repaint the same window with the new textual information?
>(ii) HOW SHOULD I CREATE A CHILD WINDOW? 
>(iii) HOW SHOULD I REPAINT AN EXISTING WINDOW?
>(iv)   I tried giving 
>         WinPostMessage(hwnd, WM_ERASEWINDOW, (MPARAM) 0, (MPARAM)0);
>in order to clear the window so that I can put new textual
>information on the same window.  But the compiler complains
>that WM_ERASEWINDOW should be declared.  ( I had defined INCL_WIN, INCL_GPI).

To clear the current window, you should invalidate the contents (with
a WinInvalidateRect(...) call.  This will declare the region you want
(which you should make the entire window) invalid and will send you a
WM_PAINT message.  Then your WM_PAINT handling section of the message
handler can erase the region and draw the next screen using
appropriate GPI calls.

One other thing:  Don't make the user press a key.  This is PM.
Provide a button of some kind to click on.  You can always link a
keystroke to this button if you want to.
-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"