I won't lie, having such troubles with my math was frustrating to the point of quitting all development on the app.
Thanks to you guys and a little programmer idiom Rubber Duck Debugging , I've found renewed interest in developing the app.
While I still don't have a version available for you guys to view, I have a few quiet days ahead of me at work, and I'll be working on it throughout the week. You can expect to see a test version ready in the next few days.
I will warn you guys (and this is important), during the development of this app, I have had a few instances of spending MANY more api credits than expected. While I will make every attempt to avoid distributing a version that has such an issue, I can't promise it won't happen. You have been warned, and in the event that such a thing *DOES* happen and, assuming it's reported quickly, I can probably get it sorted out quickly.
Finally, if anyone wants to contribute anything, feature requests, code, memes, etc. feel free to do so.
make dummy URL thay outout API (static) and you will not lose any credit, if all smooth then replace it with original API URL IMHO
ReplyDeleteThe issue was caused when an asynchronous task I had created for the purpose of collecting the API data was running itself over and over (damn you recursion).
ReplyDeleteI've sorted that issue, and now that task is only run when each page of the app is manually refreshed.