On Sunday 10 November 2002 20:22, Havoc Pennington wrote: > Here is a proof-of-concept rough cut at an extension to track "damage > regions" for the screen (notify clients about pixels that have > changed).
Great! This can be really useful for me... > The damage extension will probably become obsolete when the server has > built-in facilities for syncing the contents of one window to another > window or a shared image, including optional scaling prior to sync. Even then applications like VNC servers or 'screen cams' still need to be notified which region has changed, because they are interested in the changes, not in the result. > 1) Should there be a single atomic operation to not only get and reset > the damage region, but also GetImage the damage region? I don't At least for my use cases this is not necessary. The only disadvantage is that screen changes between receiving the DamageNotify and the GetImage cause an unnecessary DamageNotify event. This will not happen very often. > 2) What exactly are the semantics of DamageNotify events? > Are they sent: > a) whenever the damage region goes from empty to non-empty > b) whenever the damage region changes > c) whenever the bounding box of the damage region changes > d) whenever the damage region changes, but with some > (client-configurable?) rate limit > e) whenever the damage region region changes by > some (client-configurable?) area increment? > Currently the implementation does b), but this creates > a *lot* of events. For my apps a) would be ideal, possibly with a minimum interval between the events (for example for 25 fps I could then chose a 40 ms interval). bye... _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
