Threading Problem

[GoogleCodeExporter]

Problem:

If you are on a slow connection (GPRS as an example) and the application is 
currently downloading bus times for a stop, you quickly "go back" and into 
another stop the previous stop details are shown where the new stop's details 
should be.

Fix:

1) Remote "getInstance" from the download thread to stop it enforcing the "one 
thread only" policy.
2) Before each thread returns its value, check to see if the thread has been 
"interrupted()".
3) When you press back button on each stop's "view bus time" page, call 
interrupt() on the current active thread.

Overview:

Each thread should perform its own operations and deal with its own death 
rather than being "FORCED" into the same line of execution as the main 
application.

Original issue reported on code.google.com by scottast...@gmail.com on 17 Jan 2011 at 8:31

[GoogleCodeExporter]

This problem has been discussed and work is now commencing on this issue.

Original comment by riverni...@gmail.com on 24 Jan 2011 at 11:07

• Changed state: Started
• Added labels: Component-Client, Component-Logic, Component-UI, Milestone-Release0.0.4, OpSys-Android, Usability

[GoogleCodeExporter]

This issue has been fixed in r53.

Thank you to Scott Straughan for pointing this out and helping with the fix.

Original comment by riverni...@gmail.com on 24 Jan 2011 at 11:37

• Changed state: Fixed