Hi,
- For density, you don't -need- to do anything. You can let scaling happen
for you. You can think of this as writing a game for a desktop where you
set the screen resolution to some fixed size (in that case the user's screen
does the scaling).
I would like to use the vast area of the
Thanks, Lance. That works well.
So currently if I want to handle compatibility for normal size or
larger I have to launch and test my app in the HVGA emulator skin, the
WVGA800, the WVGA854, and then launch the 1.5 emulator skin by itself,
manually install my app from the command line and test
I took a crack at writing up the issue in Eclipse here:
http://code.google.com/p/android/issues/detail?id=4303
On Oct 19, 5:12 pm, polyclefsoftware dja...@gmail.com wrote:
Here's the problem I'm running into:
I'm using a resource directory qualifier (e.g. res/drawable-hdpi/).
Per the
On Tue, Oct 20, 2009 at 7:25 AM, polyclefsoftware dja...@gmail.com wrote:
When I first started Android development, I was a bit worried about
how things would progress as new hardware configurations came out. I
hope it doesn't get any more complicated than this. My guess is that
most indie
Wouldn't an update written using the 1.6 SDK still be available to
users on 1.5 as long as you set the android:minSdkVersion attribute on
the uses-sdk element in the manifest to 3?
I know this works fine on the emulator with a 1.5 image, at least,
since that is one of the tests I ran after
Here's the problem I'm running into:
I'm using a resource directory qualifier (e.g. res/drawable-hdpi/).
Per the documentation's suggestion, I set the android:minSdkVersion to
3 and the android:targetSdkVersion to 4. In Eclipse, if I set the
Project Build Target to Android 1.5, I get an error
I used the adb -e install command with the signed exported APK as an
argument to install it on an emulator that was running using a 1.5 AVD
in my case. Maybe you can use that as a workaround for the time being.
Eclipse filtering out the 1.5 AVDs does sound troublesome if you want
to test against
What you are doing is switching between the different platform versions as a
target. If you want to build with 1.6 features but still target 1.5, then
build against 1.6 and set minSdkVersion to 3 (and of course make sure you
actually run on 1.5).
On Mon, Oct 19, 2009 at 2:12 PM, polyclefsoftware
8 matches
Mail list logo
