[ALOY-761] BlackBerry: Map annotation are not displayed if object properties are set in the view .xml
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-08-06T22:14:09.000+0000 |
| Affected Version/s | Alloy 1.2.0 |
| Fix Version/s | Alloy 1.2.0, 2013 Sprint 15 |
| Components | Titanium SDK |
| Labels | qe-closed-3.1.2, qe-manualtest |
| Reporter | Federico Casali |
| Assignee | Tony Lukasavage |
| Created | 2013-07-25T23:24:32.000+0000 |
| Updated | 2014-08-06T22:14:09.000+0000 |
Description
Problem description
Map annotation is now shown on the Map if the Annotation properties are set in the View .xml file. If set in the .tss file, annotation is correctly visible.Steps to reproduce
1. See sample code attached. 2. On BlackBerry, only the annotations with the properties only set in the index.tss file are visible.
<Annotation title="Palo Alto" latitude="37.47" longitude="-122.12"/>
and also the Required
<Require src="annotationView"/>
<Annotation id="annotation1"/>
and
<Annotation id="annotation2" platform="blackberry"/>
Attachments
| File | Date | Size |
|---|---|---|
| maps.zip | 2013-07-25T23:24:32.000+0000 | 4264492 |
| Resources.zip | 2013-07-26T00:49:27.000+0000 | 4305135 |
That's odd as there is special parsing code in annotations to convert the XML string attribute to a float. It solves the same problem on Android, which also does not accept strings as values for latitude and longitude. I'll have to investigate the generated code. [~fcasali] would it be possible for you to show me the generated code for the working and non-working version?
I've attached the generated Resource folder for the provided code in the sample and attached to the Jira. Both working and not-working annotations are in there.
Tony we could fix it on the platform side but if Alloy is already doing the conversion that is probably better.
[~rmcmahon] That's the confusing part, I'm already doing the conversion for all platforms. The API is defined as a float value in the documentation, so I would define this as Alloy's responsibility.
PR: https://github.com/appcelerator/alloy/pull/197 Functional testing can be confirmed with the steps you used to produce the error before.
Verified fixed. Titanium SDK 3.1.2.v20130808180613 Alloy 1.2.0-alpha6 Appcelerator Studio 3.1.2.201308082014 CLI 3.1.2-alpha Node 0.10.13 Closing.
Reopening for updating 'tester' field, labels and log time.