zaphod.b
5th November 2014, 18:31
Consider the following code fragment:
QNetworkProxyFactory::setUseSystemConfiguration(tr ue);
QNetworkAccessManager manager;
QNetworkProxy::ProxyType type = manager.proxy().type(); //DefaultProxy
QNetworkProxyFactory *factory = manager.proxyFactory(); //0x0
I'd expect QNetworkAccessManager to obey the internal global QNetworkProxyFactory created by QNetworkProxyFactory::setUseSystemConfiguration(tr ue), but it doesn't.
(Observed on Windows - don't know if that matters.)
Is this a bug or a feature? If a feature, what might be the reasoning?
QNetworkProxyFactory::setUseSystemConfiguration(tr ue);
QNetworkAccessManager manager;
QNetworkProxy::ProxyType type = manager.proxy().type(); //DefaultProxy
QNetworkProxyFactory *factory = manager.proxyFactory(); //0x0
I'd expect QNetworkAccessManager to obey the internal global QNetworkProxyFactory created by QNetworkProxyFactory::setUseSystemConfiguration(tr ue), but it doesn't.
(Observed on Windows - don't know if that matters.)
Is this a bug or a feature? If a feature, what might be the reasoning?