{ "id": "61171", "key": "TIMOB-539", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11223", "name": "Release 1.3.0", "archived": true, "released": true, "releaseDate": "2010-05-05" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:53:26.000+0000", "created": "2011-04-15T02:31:24.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "defect", "ios", "iphone", "label", "tableview", "text" ], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:53:26.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}

Hi,

\n

I've seen this happen a few times. When I load at the vertical\nlayout demo in KS (on indeed my own app which uses this layout) the\ntext labels are nice and crisp.

\n

If I then scroll the rows up out of view - and then back in to\nview, the text is slightly blurred. (Called anti-aliasing)

\n

I have a feeling this is happening when the row is repainted as\nit comes back in to view and the calculations for the rowheight\nmight be float values, instead of integers (as we use when we set\npositions for our labels - in whole numbers)

\n

The reason I think it's this, is that this used to happen a lot\nwith Flash development - especially with certain types of text. We\nhad to make sure the positioning of the text was exactly 'on the\npixel'.

\n

Probably this could be easily fixed (by Blain?) in\nTiUITableViewRowProxy.m ?? :)

{html}", "attachment": [ { "id": "17865", "filename": "blurring.jpg", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:24.000+0000", "size": 213277, "mimeType": "image/jpeg" }, { "id": "17864", "filename": "tableview_blurringjs.zip", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:24.000+0000", "size": 3887, "mimeType": "application/zip" } ], "flagged": false, "summary": "Text anti-aliasing on tableView labels after scrolling back on to the screen", "creator": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "subtasks": [], "reporter": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "environment": null, "comment": { "comments": [ { "id": "123503", "author": { "name": "jamesk", "key": "jamesk", "displayName": "James K", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

I am encountering this problem regularly.

\n

It only happens for labels added to table view rows - not for\nnative title text.

\n

Whether it happens for a particular label appears to be\ninfluenced by the extent to which the label text is constrained by\ntop, bottom, left,\nright, width and height.

\n

Setting both left and right in\nconjunction with width:auto seems to create the\nproblem, but sometimes it's okay if you only set two of those three\nproperties (which then precludes some complex layouts).

{html}", "updateAuthor": { "name": "jamesk", "key": "jamesk", "displayName": "James K", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:31:25.000+0000", "updated": "2011-04-15T02:31:25.000+0000" }, { "id": "123504", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "body": "{html}

thanks for this info.

\n

I tried just using 2 settings - an absolute left and an auto\nheight (with textAlign:left) and I still the blurring when the row\ncomes back in to view after scrolling off.

\n

I'm also placing my labels etc. in the row within a vertical\nlayout view.

{html}", "updateAuthor": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:25.000+0000", "updated": "2011-04-15T02:31:25.000+0000" }, { "id": "123505", "author": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

Should be fixed by #722. Please test.

{html}", "updateAuthor": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:31:25.000+0000", "updated": "2011-04-15T02:31:25.000+0000" }, { "id": "123506", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "body": "{html}

Hi,

\n

I'm still seeing it happen after building the latest 1.2.0\ntoday.

\n

Oddly, I'm sometimes seeing it blurred before scrolling\noffscreen, then sharpening up after scrolling off and on again.

\n

I've also tried setting my labels to even number positions and\nwidths.

\n

Also bear in mind (if it's worth mentioning) that I use these\nlabels (of varying fontSize and fontWeight, though I have tried\nsetting fontSize to even numbers too) in a tableView WITHIN a\n'vertical' layout view (with 'auto' height) - and usually with\ntextAlign left - WITHIN each tableViewRow

\n

See the attached image, where the top three rows have been\nscrolled out and then in to view.

\n

The titles have got blurred, yet the 'time ago' labels have got\nsharper.

{html}", "updateAuthor": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:25.000+0000", "updated": "2011-04-15T02:31:25.000+0000" }, { "id": "123507", "author": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

There is a chance that this is also related to #709.\nTableRowViews are handled differently than other views because they\nare dynamically loaded. Keep this a separate issue from #722.

{html}", "updateAuthor": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:31:26.000+0000", "updated": "2011-04-15T02:31:26.000+0000" }, { "id": "123508", "author": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

Please provide me with some sample code so that I can replicate\nthe problem.

{html}", "updateAuthor": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:31:26.000+0000", "updated": "2011-04-15T02:31:26.000+0000" }, { "id": "123509", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "body": "{html}

Hi Stephen.

\n

Here you go. See attached zip. (I have removed some of the\nfunctionality of this page in my app - which loads some JSON from\nmy server and displays a tableView. You should be able to load it\nfine though)

\n

Scroll the rows up and down and you should see the effects on\nthe various labels used.

\n

thx
\nKosso

{html}", "updateAuthor": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:26.000+0000", "updated": "2011-04-15T02:31:26.000+0000" }, { "id": "123510", "author": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "body": "{html}

(from [e4650d92e0a3192a758e8fae9ea38001f6bc529c])\nCloses #539. Bounds/Frames for UILabels always need to\nbe on integer boundaries in the largest possible frame of\nreference. \nhttp://github.com/appcelerator/titanium_mobile/commit/e4650d92e0a31...

{html}", "updateAuthor": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:31:26.000+0000", "updated": "2011-04-15T02:31:26.000+0000" }, { "id": "123511", "author": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "body": "{html}

I'm still seeing this occur in places where left, right, height,\ntop or bottom are odd numbers (with textAlign right or left) - in\nplaces like vertical layout scrollViews, tableViews,\nactivityIndicator messages and others.

\n

Making sure things are on even numbers seems to help.

\n

It's got much better though. ;)

{html}", "updateAuthor": { "name": "kosso", "key": "kosso", "displayName": "kosso", "active": true, "timeZone": "Europe/London" }, "created": "2011-04-15T02:31:26.000+0000", "updated": "2011-04-15T02:31:26.000+0000" } ], "maxResults": 9, "total": 9, "startAt": 0 } } }