Better indication that host are really dont answer / not exists / etc / instead of 0ms with empty chart [windows]

[user9931]

Maybe its windows-only?

as in the title

how one can say whats going on - the app shows 0ns dots and nothing, while windows's ping different replies why the host cant be reach. It will he helpful to see those replies or something like that without need to run regular ping before gping

[immanuelfodor]

Same on Linux. I'm using gping to monitor a flaky 4G connection, and it would be absolutely useful to mark these no reply dots with another color instead of just continuing the graph with the same color. This is even more annoying when the time is more than the default 30s, eg. 5 minutes. In this case, you can't easily spot the continuation (connection/packet loss) vs. the normal results. A different color could make things a lot easier for visual debug on the history.

[myarcana]

Maybe display a different terminal background color in that column of the graph terminal, and not plot anything at all. But in this case, when the buffer is very large, the width of a column is much wider than a single data point should be.

Perhaps don't plot anything in the graph, and mark exes x on the bottom axis?

[MoralCode]

I made a demo showing how you can use multiple colors (by splitting the data into multiple datasets) at https://github.com/MoralCode/TUI-coolors-demo

[MoralCode]

Also tried to hack this into gping at https://github.com/MoralCode/gping/tree/colors but i think i keep hitting a wall with rust borrowing and lifetimes