Opened 5 years ago
Closed 5 years ago
#1077 closed enhancement (fixed)
ability to manually control the batch delay at runtime
Reported by: | Antoine Martin | Owned by: | Calvin Ko |
---|---|---|---|
Priority: | major | Milestone: | 0.17 |
Component: | server | Version: | trunk |
Keywords: | Cc: |
Description
So that applications can tell us when things don't need refreshing so much.
Change History (3)
comment:1 Changed 5 years ago by
Owner: | changed from Antoine Martin to Calvin Ko |
---|
comment:3 Changed 5 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
OK, closing. Feel free to re-open if you need more.
Note: See
TracTickets for help on using
tickets.
r11606 adds the required functions to both "xpra control" and the server dbus interface (#904).
Example usage: say you want to temporarily cap screen updates at 10fps, you would:
LockBatchDelay(wid, 100)
to force batching at 100ms minimum (note: we don't allow the batch delay to be set lower than what the heuristics have set previously, as they're very rarely wrong, and tend to underestimate anyway)UnlockBatchDelay(wid)
when the storm has passedThe control interface also supports the "*" syntax to mean all windows. With dbus, you have to specify individual windows by id.
@calvinko: is that enough for your needs?