detect bad connection and warn the user
|Reported by:||Antoine Martin||Owned by:||Antoine Martin|
When we encounter network problems, we currently deal with it by lowering the framerate (sometimes too much) and drawing spinners on top of the windows.
In some cases, the user might be tempted to blame xpra when in fact it is the network that is the problem, so we should warn the user instead and tell them where to look for the problem.
Here is an obvious symptom:
Where we just can't send the packets out.
We should probably wait a little while to see if the network problem resolves itself rather than spamming the user. And make it an option? (or just tune the sensitivity? someone on 3G may care a lot less about notifications than when on a LAN)
Change History (7)
comment:1 Changed 3 years ago by
|Milestone:||0.11 → 0.12|
|Owner:||changed from Antoine Martin to Antoine Martin|
|Status:||new → assigned|