Sam Hocevar
|
5269cad56c
|
Allow to temporarily disable dirty rectangle handling. This allows for huge
speedups when the calling application knows the dirty rectangle covered by
a complex operation.
|
15 years ago |
Sam Hocevar
|
69d8bbeb08
|
More complex dirty rectangle merging strategy. It's a lot slower in some
cases, but that can be fixed.
|
15 years ago |
Pascal Terjan
|
bd1c1cdda6
|
* Inform code reader that current algorithm is wrong
|
15 years ago |
Sam Hocevar
|
10719139e6
|
Store dirty rectangles in a structure list. For now there is still only
one dirty rectangle, but this is the first step to improvement.
|
15 years ago |
Sam Hocevar
|
ea99175a2f
|
Change the dirty rectangle API once again so that calling applications get
a more natural (x,y,w,h) 4-tuple to handle.
|
15 years ago |
Sam Hocevar
|
3338776b44
|
Fix a few DOS compilation warnings.
|
15 years ago |
Sam Hocevar
|
dd48fb62b3
|
Optimise the dirty rectangle handling by keeping track of the number of
currently dirty rectangles.
|
15 years ago |
Sam Hocevar
|
a6b98c2518
|
Change the dirty rectangle API so that it can handle several rectangles. The
inner implementation still only handles one dirty rectangle, but this way
we can prepare supporting applictions for the future.
|
15 years ago |