[TIMOB-9063] TableViewRow: Check Mark Does Not Appear On QVGA Screens
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Won't Do |
Resolution Date | 2020-01-10T18:07:17.000+0000 |
Affected Version/s | Release 2.0.0, Release 3.1.0 |
Fix Version/s | n/a |
Components | Android |
Labels | api |
Reporter | Dário Marcelino |
Assignee | Unknown |
Created | 2012-05-07T06:20:56.000+0000 |
Updated | 2020-01-10T18:07:17.000+0000 |
Description
Check mark doesn't appear on QVGA screens.
Check this question: http://developer.appcelerator.com/question/131811/check-mark-does-not-appear-on-qvga-simulator
Or just try this code:
~~~
Ti.UI.setBackgroundColor('#000');
var win = Ti.UI.createWindow();
var parentView = Ti.UI.createView();
// Create a TableView.
var aTableView = Ti.UI.createTableView();
// Populate the TableView data.
var data = [
{title:'Row 1', hasChild:true, color:'red', header:'First'},
{title:'Row 2', hasDetail:true, color:'green'},
{title:'Row 3', hasCheck:true, color:'blue', header:'Second'},
{title:'Row 4', color:'orange'}
];
aTableView.setData(data);
// Listen for click events.
aTableView.addEventListener('click', function(e) {
alert('title: \'' + e.row.title + '\', section: \'' + e.section.headerTitle + '\', index: ' + e.index);
});
// Add to the parent view.
parentView.add(aTableView);
win.add(parentView);
win.open();
~~~
The check mark does show up in larger screens but not on QVGA.
The problem reproduces with release 3.0.2 and master release 3.1.0. It works properly on screens 320x480 and larger in the simulator but the same code on the 240x320 QVGA does not display the check mark. tested on Titanium Studio, build: 3.0.2.201302191606 Titanium SDK version: 3.1.0 Titanium SDK version: 3.0.2 Device: Samsung galaxy s duos Android version: 4.0.4 Android Emulator: Android SDK version: 2.2
This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.