Bug: wired connection is shown as "Ping: none"

[bersbersbers]

This is my network setup as seen from tracert:

>tracert 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  10.0.0.6
  2     4 ms     2 ms     2 ms  10.0.0.1
  3    10 ms    10 ms     9 ms  xxx
  4    11 ms    11 ms    11 ms  xxx
  5    21 ms    21 ms    19 ms  xxx
  6    20 ms    20 ms    20 ms  xxx
  7    21 ms    22 ms    20 ms  172.253.64.119
  8    20 ms    20 ms    19 ms  8.8.8.8

So I have three PingoMeters running for 10.0.0.6, 10.0.0.1, and 8.8.8.8, where for first one is shown as "Ping: none" intermittently.

Could it be that the 10.0.0.6 one is too fast and is shown as "Ping: none" incorrectly? I am referring to this piece of code:

PingoMeter/NotificationIcon.cs

Lines 172 to 174 in 5bdee3b

	default:
	// OK. В остальных случиях получим исключение
	DrawGraph(reply.RoundtripTime);

PingoMeter/NotificationIcon.cs

Lines 83 to 94 in 5bdee3b

	private void DrawGraph(long value)
	{
	if (value == -1)
	{
	notifyIcon.Icon = Icon.FromHandle(hiconOriginal);
	return;
	}
	if (value == 0L)
	{
	//g.DrawLine(Pens.Black, 15, 15, 15, 1);
	notifyIcon.Text = "Ping: none";
	}

It seems to me like value == 0L is not necessarily an exception.

[bersbersbers]

Commenting out these lines fixes the issue:

PingoMeter/NotificationIcon.cs

Lines 90 to 94 in 5bdee3b

	if (value == 0L)
	{
	//g.DrawLine(Pens.Black, 15, 15, 15, 1);
	notifyIcon.Text = "Ping: none";
	}

[EFLFE]

Thanks for the report. I will fix it soon.

[EFLFE]

I think the problem is solved?

[bersbersbers]

Yes! I had re-built the app myself with the proposed fix, but I also verified 0.9.5 now and it's working well. Thank you!