View Single Post
Old 01-19-2010, 06:57 AM   #165
Antartica
Evangelist
Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.Antartica ought to be getting tired of karma fortunes by now.
 
Antartica's Avatar
 
Posts: 423
Karma: 1517132
Join Date: Jun 2006
Location: Madrid, Spain
Device: quaderno, remarkable2, yotaphone2, prs950, iliad, onhandpc, newton
Quote:
Originally Posted by tango.0309 View Post
In this case the refresh is not happening properly.
(The screen will be refrehed partly initially later fully. In case of pop up windows of our application, each window is refreshed twice)
You can try with a larger refresh timeout. In xepdmgr.c, change the line that says:

Code:
#define REFRESHTIMEOUTMS 500
To something larger, such as

Code:
#define REFRESHTIMEOUTMS 750
And see if the double refreshes disappear with that.

Rationale: After receiving a damaged area from the X server, xepdmgr waits for more damaged areas for REFRESHTIMEOUTMS milliseconds, and if no more damaged areas are received in that time period it refreshes the screen. Larger values for REFRESHTIMEOUTMS makes double-refreshes improbable, but provoke worse responsiveness. Requiring values higher than 1500 is a symptom that something is wrong, either in the app (too slow) or in xepdmgr (a timing bug?).
Antartica is offline   Reply With Quote