Minor issues in 1.544.2081
Hi,
thanks for fixing the regression that prevented extensions from drawing stuff on profile change in the March 6 update; it was difficult to work with extensions beforehand. With the 1.544.2081 version, some minor issues remain. Since the github tracker was purged, I'm posting them here:
- Sometimes, custom graphical data fields are rendered with the datafield title even though they request not to. This can then be fixed by reloading the ride profile. It looks to me like some race condition on the karoo's side. It is reproducible with the headwind extension's data fields among others.
- Sometimes, the extension's background service is not restarted after reinstalling or updating an extension. This can be frustrating, because it gives users the impression that the extension is inherently broken. I had not seen this problem on previous karoo software versions.
Best,
Tim
-
- Related to the datafield title issue: Sometimes, the custom view is rendered on top of the "No sensor" message in the same field.
- Related to another issue I had posted on the Github tracker earlier: Clickable custom fields catch the "long-press" event, so they are not replacable by the user in the profiles or in the ride app. This can be worked around for the profiles app on the extension's side by making a datafield unclickable if it is in preview mode, but this is not applicable in the ride app
Please sign in to leave a comment.
Comments
1 comment