Quote:
Originally Posted by hansel
I think the partial update stuff is fairly new. We should test it with a small program to see if it works, how it looks on the display, and how it performs...
|
Agreed :-).
Quote:
Originally Posted by hansel
Idea:
Maybe the most universal solution would be to integrate the xdamage stuff in displayMgr (make a replacement with the same name, but with extra features) - When starting displayMgr -x: your code (dedicated thread) handles the display updates directly, and disables al 'normal' updates
- when starting displayMgr in the normal way, your code is not invoked (100% compatible).
What do you think? |
Idea taken
.
The plan was to support the displayMgr protocol in xepdmgr anyway, merging the two will fulfill that neatly. I was intending to reimplement it, but after all there is no need for it (displayMgr is GPL
). Maybe I was having some NIH syndrome.
Notes:
1. Will integrate displayMgr code inside xepdmgr, as I want to keep the current main loop. But will honour displayMgr command-line as used by irex scripts.
2. No threads; personally I think that they don't worth the effort when in UNIX; too many things are non-reentrant. If needed I'll create a child process, but it doesn't look that it's needed.
Hope I have some time for it this week.