gscan: don't force host/owner vis

[matthewrmshin]

Don't force host/owner visibility in multi-host/owner modes. (Ref #2096.)

[oliver-sanders]

Isn't the new behaviour that the host column is ONLY visible if hosts are provided as command line arguments?

[matthewrmshin]

No, you can turn it on/off if you want. The new behaviour here stops it from making the host column visible automatically after each update. (Users are unable to turn it off before this change - if they have suites running on multiple hosts).

[hjoliver]

@matthewrmshin - I'm slightly confused. Contrary to your previous comment, testing conforms to your description and title which implies "host" column can't be turned off if I request a multi-host scan on the command line (cylc gscan hostA hostB). It can now be tuned off if I did not request a multi-host scan, which is an improvement on master - but shouldn't I be able to turn the host column off even if I did request a multi-host scan? (maybe I am using multiple suite hosts but am not interested in which suite is running on which host).

[matthewrmshin]

@hjoliver It can be done by simply removing the block that forces the host column to be visible. Is this what we want?

[hjoliver]

Yes, I think so.

[oliver-sanders]

Wouldn't the simplest option be to treat the host column like the others? Only display it if the user wants it displayed irrespective of how gscan was launched.

[matthewrmshin]

Done for both host and owner.

[hjoliver]

Yes, I agree with @oliver-sanders - that's what I meant in fact.

[hjoliver]

Good.