⚡️ Enhancements - UI optimizations to hide unused processes from Status tab

[Rikj000]

Enhancement request
Possible further UI enhancements:

1. Move Visible columns: to Gupaxx tab, since they're settings,
   which do not really belong under the status tab, perhaps also rename columns to processes, see 2.
2. Hide the buttons from the top if visible columns are disabled, since they're kinda useless if the process is not used.
   Forgot to mark/mention in screenshot, to also hide the status buttons at the bottom, if disabled.
3. Stretch the status columns to fit the screen, but keep a minimal width to retain readability.

Additional context

Linked feature request issue: hinto-janai#108

[Cyrix126]

1 &2: I find the buttons to be at the right place if their intent is to only hide status column. If the user hide a column, we can assume indeed that he's not using the service at all. So yes if the buttons hides/show tabs/bottom status/column, I guess it's more logical to have them in gupaxx tab. Though I like the fact to see the effect of hiding the column immediatly.

3: Not sure it's needed. Currently the user have all the data condensed, where if the columns take more width, the distance between the data would be greater and so it would take more work for the eyes to find.

[Rikj000]

1 & 2: I find the buttons to be at the right place if their intent is to only hide status column.
... I like the fact to see the effect of hiding the column immediately.

Indeed, in it's current state the buttons do make sense under the Status tab,
since they only hide/show information under that tab.

If the user hide a column, we can assume indeed that he's not using the service at all.
So yes if the buttons hides/show tabs/bottom status/column, I guess it's more logical to have them in gupaxx tab.

If you'd also hide the buttons at the top + runtime status at the bottom when disabling them,
then in my opinion it would make more sense to have them under the Gupaxx tab.
Since then they do not only apply to the Status tab anymore, but instead will have effect upon the whole application.

3: Not sure it's needed. Currently the user have all the data condensed, where if the columns take more width, the distance between the data would be greater and so it would take more work for the eyes to find.

That's a fair point, I've altered my original post so 3. is now strike-through.