I agree that the tri-state enum is useless. But the shell can't magically fix it, I suspect. The best option is probably to just assume that "Unknown" means the the same thing as "Not accessible". If bad things happen that way, so be it: inside the scope is the wrong place to fix this. It needs to be fixed in QNetworkAccessManager. (Failing that, maybe in the shell, but that still smells bad.)
The tri-state accessibility comes straight from QNetworkAccessM anager: http:// doc.qt. io/qt-5/ qnetworkaccessm anager. html#NetworkAcc essibility- enum
There is a discussion thread here: http:// www.qtcentre. org/threads/ 37514-use- of-QNetworkAcce ssManager- networkAccessib le
I agree that the tri-state enum is useless. But the shell can't magically fix it, I suspect. The best option is probably to just assume that "Unknown" means the the same thing as "Not accessible". If bad things happen that way, so be it: inside the scope is the wrong place to fix this. It needs to be fixed in QNetworkAccessM anager. (Failing that, maybe in the shell, but that still smells bad.)