05-29-2025, 11:13 AM
This version is now running:
TIWIPGeolocationClient* pCurClient;
TIWIPGeolocationClient::MaxErrorCount = 10;
TIWIPGeolocationClient::Enabled = false;
if((pCurClient = new TIWIPGeolocationClient(this)) != NULL)
{
// Interface and key
pCurClient->IPGeoApiInterface = TIPGeoApiInterface(CurIndex);
pCurClient->ApiKey = theApiKey;
// Execute GeoApi function
if(pCurClient->Execute(theIPAddress) == true)
{
// Retrieve API response
}
}
In my opinion, the changes made to the general component TIWIPGeolocationClient for the version IW16.0.9 are certainly very helpful for the component developer's testing,
but may be rather hindering for practical use due to the implicit error handling.
A component developer should not make any assumptions about how his component will ultimately be used in an application environment.
TIWIPGeolocationClient* pCurClient;
TIWIPGeolocationClient::MaxErrorCount = 10;
TIWIPGeolocationClient::Enabled = false;
if((pCurClient = new TIWIPGeolocationClient(this)) != NULL)
{
// Interface and key
pCurClient->IPGeoApiInterface = TIPGeoApiInterface(CurIndex);
pCurClient->ApiKey = theApiKey;
// Execute GeoApi function
if(pCurClient->Execute(theIPAddress) == true)
{
// Retrieve API response
}
}
In my opinion, the changes made to the general component TIWIPGeolocationClient for the version IW16.0.9 are certainly very helpful for the component developer's testing,
but may be rather hindering for practical use due to the implicit error handling.
A component developer should not make any assumptions about how his component will ultimately be used in an application environment.

