View Single Post
Old 01-07-2010, 05:04 AM   #163
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
I want to send damage events to "xepdmgr" with (x,y) coordinates and (width,height) of the damaged region.The present "xepdmgrclient.c" is sending only property event. I found in xepdmgr is capable of receiving damage events. I am not clear in sending damage event to xepdmgr, whether any changes required in xepdmgr server side also.
You have some misconception: xepdmgr makes screen updates automatic, as in "the app doesn't need to send damage events to xepdmgr".

xpedmgr gets the damage events directly from the X server.

xepdmgrclient implements a protocol to send some messages to xepdmgr to optimize the screen refresh, but it is not needed for the basic operation.

xepdmgrclient exists because it is very common for a reader application to update the entire screen with a new page of content and wanting to display it ASAP, not wanting the timeout to pool requests that xepdmgr uses in its "autonomous" operation. Also xepdmgrclient makes possible to avoid double-refreshes by signaling xpedmgr to "freeze" the display while doing some slow screen update, and "thaw" it after the drawing has finalised, hence updating the display only once (this is only useful for screen updates that are longer to perform than the xepdmgr timeouts, that are 500ms in the current 1.9i implementation).

Quote:
note:
I am exploring "xepdmgr-1.0-iliad" code.
Please, use version 1.9i as it fixes numerous bugs compared to 1.0 version. It is available in the following post (it has sources included):

https://www.mobileread.com/forums/sho...&postcount=146

If you have additional questions, don't hesitate to ask.

Best regards,
Antartica.
Antartica is offline   Reply With Quote