[TIMOB-1241] Android: anyDensity == true issues
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:55:37.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 M02 |
| Components | Android |
| Labels | android, feature |
| Reporter | Don Thorp |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T02:47:27.000+0000 |
| Updated | 2011-04-17T01:55:37.000+0000 |
Description
There are several issues that appear when a custom AndroidManifest is used to specify that any density is supported. Tab Widget doesn't display correctly and text fields / fonts don't play well with others. The attached project shows some of the issues.
Marking as a feature since we don't currently include this in testing. There may be other issues once we do.
Also, See http://developer.appcelerator.com/helpdesk/view/25771">HelpDesk Ticket 25771 for more information wrt to edit fields and layout.
Attachments
| File | Date | Size |
|---|---|---|
| screentest.zip | 2011-04-15T02:47:28.000+0000 | 5154736 |
The specific test you included looks fine on my Evo. The TextView has a built-in margin around it's border that makes it look artificially small compared to a guide that's only slightly bigger. If you expand the size to a few hundred pixels, it scales with the size of the guide (keeping the same margin size). I've ran KitchenSink with anyDensity="true" and I don't notice any glaring problems other than smaller tab and tableview images, which should be expected. Marking as needs more info. We should probably open separate tickets for each defect that we run into that instead of having one all-encompassing issue like this anyway.