We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.0.38 docs state:
Ruby: Geolocation.set_notification_ex(callback url, string callbackParams, options hash) JavaScript: Rho.Geolocation.set_notification_ex(callback url, string callbackParams, options hash);
Ruby: Geolocation.set_notification_ex(callback url, string callbackParams, options hash)
JavaScript: Rho.Geolocation.set_notification_ex(callback url, string callbackParams, options hash);
iOS implementation punts by simply calling set_notification. But mis-match in type of third parameter:
set_notification
void rho_geo_set_notification_ex(const char *url, rho_param* p, char* params) { //TODO: rho_geo_set_notification_ex }
IMO, this is a bug, and I will file an Issue for that.
But the documentation should correspond with reality. At least a note about the bug. It should be stated that this is not implemented for iOS.
Don't know about other platforms.
The text was updated successfully, but these errors were encountered:
rhomobile/rhodes#635
Sorry, something went wrong.
I wasn't very observant!
It doesn't punt to set_notification. It does nothing, and of course will still throw a run-time error if the third parameter is a hash.
Definitely should be documented as "not implemented" for iOS!
No branches or pull requests
5.0.38 docs state:
iOS implementation punts by simply calling
set_notification
. But mis-match in type of third parameter:IMO, this is a bug, and I will file an Issue for that.
But the documentation should correspond with reality. At least a note about the bug. It should be stated that this is not implemented for iOS.
Don't know about other platforms.
The text was updated successfully, but these errors were encountered: