I am trying to place a background image within a HorizontalScrollView
such that the entire width of my image is scrollable and such that the
excess height will be cropped. This seems like it should be
straightforward: no scaling, no centering... just peg it to the bottom
left corner and lop off the
Thanks for the insights! I had been using 1.6, so this is exactly what
I wanted to hear :)
... on to 2.0
On Nov 9, 9:34 am, Romain Guy wrote:
> Yes, it only applies to 2.0.
>
>
>
> On Mon, Nov 9, 2009 at 12:26 AM, String wrote:
> > On Nov 9, 3:26 am, Romain Guy wrote:
>
> >> Devices running in
or hw.ramSize say?
> -Dan
>
> On Sun, Nov 8, 2009 at 6:36 PM, knavewave wrote:
> > Just started testing support for multiple screen sizes via emulator,
> > and noticed that I am getting these lovely 'bitmap size exceeds VM
> > budget' crashes when flipping the or
Just started testing support for multiple screen sizes via emulator,
and noticed that I am getting these lovely 'bitmap size exceeds VM
budget' crashes when flipping the orientation. Since all of this works
on m G1 (my test is to do 25 quick orientation flips), I am growing
suspicious that the addi
Thanks for the comments everyone.
RichardC, the idea is not so much to tie the app to a particular
device, as it is to confirm that the device signing up for an account
is the same one that purchased the app. Basically, what I am trying to
do is have my app transparently link the account signup (
I am preparing to deploy a service based (account info / functionality
provided via my server) app via the standard android market / google
checkout approach, and am curious to see if anyone has had success or
can propose suggestions on how to associate market purchases with
individual devices.
T
6 matches
Mail list logo
