Making the debug tab autofresh (suggested by @fekt) sounds like a useful feature. I think it it should default to OFF and have a little binary toggle on the debug tab to enable it. We can either let the user choose a custom refresh interval or just have some reasonable default, like once per minute.
The reason to default it to OFF is many/most users probably never look at the debug log. We could also potentially make it so the autorefresh only happens if the debug tab is "active" (being looked at) so it's not doing lots of useless work that could potentially slow down mining.
Making the debug tab autofresh (suggested by @fekt) sounds like a useful feature. I think it it should default to OFF and have a little binary toggle on the debug tab to enable it. We can either let the user choose a custom refresh interval or just have some reasonable default, like once per minute.
The reason to default it to OFF is many/most users probably never look at the debug log. We could also potentially make it so the autorefresh only happens if the debug tab is "active" (being looked at) so it's not doing lots of useless work that could potentially slow down mining.
Making the debug tab autofresh (suggested by @fekt) sounds like a useful feature. I think it it should default to OFF and have a little binary toggle on the debug tab to enable it. We can either let the user choose a custom refresh interval or just have some reasonable default, like once per minute.
The reason to default it to OFF is many/most users probably never look at the debug log. We could also potentially make it so the autorefresh only happens if the debug tab is "active" (being looked at) so it's not doing lots of useless work that could potentially slow down mining.