Quote:
Originally Posted by sphaero
I've tested version 1.9e
|
Thanks!
Quote:
Originally Posted by sphaero
So are you suggesting to not use DisplayMgr?
|
Yes. The idea in "server mode" is to be a drop-in replacement for displayMgr; using xepdmgr to talk with the delta driver directly.
But there are some problems to resolve yet in server mode:
1. ContentLister is not updated always (?)
2. double-refresh with ipdf when ipdf updates fbdev directly bypassing the X server
3. refreshes with the soft-keyboard (it has strange behaviour here).
It's not very simple because there is information flowing from displayMgr to and from contentLister, and I'm not sure of the rationale of it. Problem (1) and (3) are related to this.
Another thing is that when the application (ipdf) uses the "update the screen bypassing X" hack to gain 1 second in the refresh, it's not informing anyone of it (It simply assumes that if he is not signaling an update, no update will be done, and that is contrary to the intent of xepdmgr). Perhaps doing an heuristic it can be avoided, but I'm not sure if it will work correctly (as the refresh is done prior to X informing of the damaged area). I'll have to try it. This is problem (2).
And in general, I have to improve the heuristics for how much time to wait after a damaged part is detected; this wait is used to be able to bundle multiple small updates in a single screen flash, but right now is fixed.
Anther thing left is the problem of note-taking programs (scribble-like; i.e. Xournal). I've not tried to resolve that problem yet.
So, that is the current state of the program
.