home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.apps
- Path: sparky!uunet!gatech!paladin.american.edu!howland.reston.ans.net!usc!news.service.uci.edu!ucivax!ucla-cs!lanai.cs.ucla.edu!william
- From: william@lanai.cs.ucla.edu (William Cheng)
- Subject: need help on Windows 3.1 ``repaint'' problem...
- Message-ID: <1993Jan12.192446.1889@cs.ucla.edu>
- Followup-To: william@cs.ucla.edu
- Keywords: win31, windows, 3.1, repaint, borland, turbo
- Sender: usenet@cs.ucla.edu (Mr Usenet)
- Nntp-Posting-Host: lanai.cs.ucla.edu
- Organization: UCLA, Computer Science Department
- Distribution: usa
- Date: Tue, 12 Jan 93 19:24:46 GMT
- Lines: 20
-
- Hi,
- I have a ``repaint''-related problem. I'm using Borland
- compilors. The problem occurs for both the Turbo C/C++ Compilor
- (version 3.0) and the Borland C/C++ Compilor (version 3.1) under
- Windows 3.1. The problem does NOT occur for the above compilors
- under Windows 3.0.
-
- Basically, my application creates a few standalone windows.
- Among them, the one which is deepest in the stacking order does not
- get WM_PAINT messages when InvalidateRect() is called. If I select
- the deepest window, it gets the delayed WM_PAINT and WM_ERASEBKGND
- messages. Also, if one of those windows is iconified, it acts like
- the deepest window and the icon doesn't get redrawn.
-
- Does any know what can cause WM_PAINT messages not to be
- posted when InvalidateRect() is called?
- --
- Bill Cheng // UCLA Computer Science Department // (310) 645-8328
- 3564-C Boelter Hall // Los Angeles, California 90024 // USA
- william@CS.UCLA.EDU ...!{uunet|ucbvax}!cs.ucla.edu!william
-