Issue
Client had to set
explicitly in order to load the density-specific resources correctly.
Steps to reproduce
1. use demo
https://github.com/appcelerator/KitchenSink/
2. Remove from tiapp.xml
tag
3. Install & run
Expected behavior
The default is true already.
Actual behavior
The screen looks scaled (like if anyDensity true wasn't honored).
Additional details
They used
17 and
.
They have to include
in order to get correct resources on devices of different resolutions.
Tested on
tested on a xhdpi device, android 4.1.2 a S3 as well as new htc one.
If they don't include
, the app is displayed with mdpi assets. If they include
, the app is displayed correctly with xhdpi assets.
They use unit "dp" in all places of their code.
Right now this isn't an issue for their app because they can simply include
for everything to work.
Documentation
The Titanium project was clean up as our docs say:
"You may or may not need to clean your project (force Titanium to freshly re-generate the native project files) to ensure your new configuration settings are picked up"
-
http://docs.appcelerator.com/titanium/latest/#!/guide/Using_density-specific_resources_on_Android-section-29004808_Usingdensity-specificresourcesonAndroid-DisablingMultipleDensityHandling
This ticket is something to consider when working on the Titanium Asset Management System (TIMOB-19298).
Resolving ticket as Invalid as there is now a new version of Kitchen Sink available and we no longer support the version which relates to this ticket.