Ping sensor, fixes #72

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.

[ewired]

Thoroughly tested ping sensor based on a ping subprocess. If your update interval is set to 3 seconds and a ping doesn't respond by the next interval, it will display 3000+ ms and end the subprocess early, otherwise falling back to the max ping timeout of 5 seconds which will display 5000+ ms. Upon error (no DNS resolution, invalid host, etc) it displays ?? ms. I wanted to make sure the user gets a chance to fully type the intended host before confirming, so the prefs may be a bit unique compared to other features. It is lacking a unique icon for the original icon set, I just copied the cloud icon. Tested on NixOS.

[ewired]

After many weeks of usage I found out that clicking to open the menu was causing it to report 5000+ ms even if it had not been 5 seconds since the last click without a ping response. I would rather it show the ms since the last ping attempt with a + in that case, taking to drafts until I get a chance to fix that.