Acceptance Mark

JBlueLineAE - Android Edition

Version History

0.1 - October 2009
Public beta release.
0.3 - November 2009
Public beta release.
0.4 - 3 January 2010
Fixed a bug with derivation of calls for methods like Grandsire Minor.
1.0.0 - 7 October 2011
Fixed what appears to be an problem with the APIs for version 1.5 where on newer devices the screen size is not correctly reported. From now on the minimum operating system version is Android 1.6. This is not expected to cause many people a problem (if any).
1.1.0 - 31 December 2012
Trying to make the software friendly to larger screens as found on tablets. This means having inital drawing sizes more appropriately chosen, and when 'ringing' a method, the layout needs to be less sparse. The updated "System Design Kit" (SDK) now includes an Android 'lint' (code checker) that was very forthcoming with 'suggestions' on how the code would be better. These points have been addressed, e.g. 'Cancel' buttons before 'OK' buttons, and more efficient layouts for the screen.
1.2.0 - 5 January 2013
Identified and fixed a serious flaw in the software affecting busy devices that are continuously closing activities down to re-use resources for foreground applications. The bug came to light when searching the library for a method (either by collection of sub-string) and the software refused to change to the selected method, preferring to crash and return to the display of the existing method. With thanks to a patient customer who provided remote testing to locate a problem that was not reproducable locally on the same make & model of phone.
1.3.0 - 30 July 2013
Android 3.0 (API version 11) uses hardware graphics acceleration by default. This increases the memory usage and limits the canvas size for drawing methods. When viewing methods on higher numbers which demand larger canvases, drawing just did not occur, and no error was raised (at least on Nexus 7 and Nexus 10 tablets) as has been the case with previous devices, and for which JBlueLine caters by falling back to a cheaper memory mode (at cost of CPU & user experience). Hardware acceleration has now been disabled for the application, as its not needed but the memory for drawing is. The method of implementing the fix means I'm keen to hear if users of older versions of Android, ver 2.x.x or lower, experience any problems running the software, as I can only 'emulate' the software on an older device.
1.4.0 - 25 March 2014
Fixed the text size used when ringing a method. Text displayed on the more modern larger screens was too small to be readable, this has now been future proofed to some extent. Also fixed the volume control for beeps so that it works of the standard volume setting buttons rather than an internal option to be set. No idea why this has not always been the case.

Validate HTML