Skip to content

Conversation

@danxuliu
Copy link
Member

@danxuliu danxuliu commented Jul 14, 2020

Requires #3926

Backport of #3839, #3911 and #3907

danxuliu and others added 19 commits July 21, 2020 10:20
A high round trip time means that there is a delay in the connection,
which is in itself bad (specially in a conversation instead of in a
"monologue").

Besides that a delay in the connection can also cause that some packets,
even if they are not lost, are discarded anyway to try to keep the
playing rate in real time.

The round trip time is only available for sent data, but not received
data.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Currently "setScreenPeer" is only called with actual objects, never
null, but just in case for the future.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
This will allow to get those attributes from other objects, as well as
trigger an event when they are changed.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
If the quality was seen as very bad for a split second this showed and
quickly hidden again the quality warning, which is annoying as it may
not be possible to even read the tooltip. To mitigate that now the
quality warning is shown at least for 3 seconds before hiding it again.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
In some cases the warning could be repeteadly shown and hidden again. In
those cases showing the warning is fine, but showing the tooltip could
be annoying. Therefore now the tooltip is automatically shown only if
the warning has not been recently shown. In any case, the tooltip can
still be shown when hovering on the warning.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
The event listeners where not properly stopped when a Peer was set, so
if the same Peer was set twice the listeners were duplicated, which in
turn could lead to errors due to only one of them being removed.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Instead of showing the quality warning tooltip only if it has not been
recently shown now the quality warning tooltip is always shown when
the quality warning is shown, except if the user has explicitly
dismissed it.

Signed-off-by: Marco Ambrosini <[email protected]>
@danxuliu danxuliu force-pushed the backport/3839/stable18-warn-user-on-high-load branch from a53dd1f to 1bff844 Compare July 21, 2020 08:21
@nickvergessen nickvergessen merged commit 10a2e0e into stable18 Jul 21, 2020
@nickvergessen nickvergessen deleted the backport/3839/stable18-warn-user-on-high-load branch July 21, 2020 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants