[TIMOB-4124] Cache custom fonts when they are loaded the first time
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-05-24T11:30:50.000+0000 |
| Affected Version/s | Release 1.7.0, Sprint 2011-20 |
| Fix Version/s | Release 1.7.0, Sprint 2011-20 |
| Components | Android |
| Labels | n/a |
| Reporter | Opie Cyrus |
| Assignee | Opie Cyrus |
| Created | 2011-05-17T15:53:53.000+0000 |
| Updated | 2011-05-24T11:30:50.000+0000 |
Description
Attachments
| File | Date | Size |
|---|---|---|
| scrollPerf.js | 2011-05-17T16:19:55.000+0000 | 4276 |
Issue can be verified using attached test app. Basically, setup a custom font as mentioned in ticket #3418 Once a custom font is setup in your Resources/fonts directory, run the test 3 times with the 'myFont' variable set to 'monospace', 'does not exist' and then your custom font. You should see monospace font used the first time, default font used the second and then your custom font used the third time. Scrolling performance should be smooth (within reason) for all three scenarios.
test app
logged time includes all investigation, source change and testing of various test cases.
Verified all three options in test app work as expected. Scrolling performance good in all cases. Used Nexus S and Eris.