destination unreachable is undistinguishable from long latency

Bug #202152 reported by TomasHnyk
2
Affects Status Importance Assigned to Milestone
Link Monitor Applet
Confirmed
Wishlist
Unassigned

Bug Description

First of all, thanks for the 3.0 version, it no longer crashes. However, I think that the feature of 2.2 that the bars went red when the link was down and orange when the latency was high was better than current state when these two are undistinguishable.

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

Bars never went orange when the latency was high.

Changed in link-monitor-applet:
status: New → Invalid
Revision history for this message
TomasHnyk (sup) wrote :

I use human theme, so they did go orange. By all means, at least under human theme, one could easily know whether the connection is just slow or down (red when it was down, orange or other colour depending on the theme (I guess the second one, I never use other themes)) which was quite handy. That functionality is now lost.
If you want me, I will provide you with screenshots how it looked like.

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

No functionality was lost. A bar which was red in previous versions is now outlined.

Revision history for this message
TomasHnyk (sup) wrote :

Oh, I see now. Sorry for disturbing then.

Revision history for this message
Octavio Alvarez (alvarezp) wrote :

Jean-Yves, I beg to differ: there *is* loss of functionality.

Even though technically speaking, l-m-a does its job by giving some feedback about a down link by outlining it, previous versions were noisy about it. Now, 3.0 just doesn't attract my attention to problematic links anymore.

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

Feel free to suggest a better indicator. A red bar is no longer an option since 3.0 supports custom colors.

Revision history for this message
Octavio Alvarez (alvarezp) wrote : Re: [Bug 202152] Re: destination unreachable is undistinguishable from long latency

On Sun, 2008-05-04 at 21:07 +0000, Jean-Yves Lefort wrote:
> Feel free to suggest a better indicator. A red bar is no longer an
> option since 3.0 supports custom colors.

Brainstorming:

1. The new outline rectangle could turn red.

2. The new outline rectangle and the l-m-a icon (only if visible) could
blink (on click, stop blinking).

3. The indicator could go up high and blink (on click, stop blinking).

... or any combination of the above.

I think an appropriate value for the blinking frequency would be 3 to 4
Hz with 50% on/off ratio.

As an addition to the mentioned above, executing a custom command would
be very nice, as audible alarms would become a possibility.

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

Ok, some sort of blinking could make sense. I will think about this.

Changed in link-monitor-applet:
importance: Undecided → Wishlist
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.