Miring dengan Suhu S

by Herawansyah, Ir., M.Sc., MT » Tue, 20 Apr 2010 00:20:25 GMT


Sponsored Links
 Sore ini akhirnya ketemu Suhu SA di Gedung Indosat Jakarta, terima kasih Suhu 
SA sehingga Nexus One saya bisa lancar jaya


Onyx : 215A943C - pMsgr :  DB8C0A8
Nexus One The Android #1 - IPhone 3G
The WranglerBerry B 16 TR - YB4MF
 http://www.herawansyah.blogspot.com 

-- 
"



Miring dengan Suhu S

by Herawansyah, Ir., M.Sc., MT » Tue, 20 Apr 2010 02:43:03 GMT


 Sore ini akhirnya ketemu Suhu SA di Gedung Indosat Jakarta, terima kasih Suhu 
SA sehingga Nexus One saya bisa lancar jaya


Onyx : 215A943C - pMsgr :  DB8C0A8
Nexus One The Android #1 - IPhone 3G
The WranglerBerry B 16 TR - YB4MF
 http://www.herawansyah.blogspot.com 

-- 
"


Sponsored Links


Miring dengan Suhu S

by Lesjaw鈩?鈾 » Tue, 20 Apr 2010 12:26:27 GMT


 Mantafs bro...sol

On Apr 20, 2010 1:42 AM, "Herawansyah, Ir., M.Sc., MT" <




Sore ini akhirnya ketemu Suhu SA di Gedung Indosat Jakarta, terima kasih
Suhu SA sehingga Nexus One...

-- 
"



Other Threads

1. Maintaining Aspect Ratio of Background Image

I've got a complex problem I've been thinking over for a while.  The
core issue is that I've got a background for my app which I would like
to maintain its aspect ratio, yet at the same time use as much of the
background as possible.  My current solution, which is less-than-
ideal, is to simply use the default android:windowBackground style,
which simply fills the background; so on some screens it looks fine,
and on others the aspect ratio is a little wonky.

One important thing to note is that the background isn't being used
for anything but as a background.  I know some people use the
background as a board for games...  this isn't a case like that.  In
this situation, the aspect ratio keeps the image looking nice, nothing
more.

Anyways, I've come upon an interim solution, which is to use a
BitmapDrawable with Gravity set on it to center.  However, while this
maintains aspect ratio, it presents a few problems:

1. I have to create multiple images, one for each possible overall
screen size (small, medium and large).

2. Depending on the image, it won't necessarily take up the entire
space.  For example, if I make a 480x854 (for Droid) background image,
some of the vertical space will be chopped off on an N1.

What I'd like - and I'm not sure if this is possible - is for the
background to fill vertically, maintain the horizontal resolution
based on the modifications made vertically, then to be centered.  In
other words, the horizontal part may be clipped, but the vertical part
will always be 100%.

Is any of this doable?  Is there a better solution to this problem I'm
not aware of?

-- 

2. negative x co-ordinate on swipe to the left

I have a list view with list item that has one CheckBox and two
TextViews. I have set on touch listener to each of these widgets. Now
when I do swipe to the right the x co-ordinates are recorded correctly
by
the onTouch event listener. When I do swipe to the left it shows
negative
value for x co-ordinate. Is this a bug or I am missing something.
My phone is motorola droid.

code
------------
public boolean onTouch(View v, MotionEvent event) {
       Log.d(TAG, "ListAdapter.onTouch x="+event.getX());
       return false;
}

result
-----------------
ListAdapter.onTouch x=1.4075205
ListAdapter.onTouch x=1.4075205
ListAdapter.onTouch x=20.879065
ListAdapter.onTouch x=120.67073
ListAdapter.onTouch x=222.89635
ListAdapter.onTouch x=349.94818
ListAdapter.onTouch x=472.1321
ListAdapter.onTouch x=472.1321

ListAdapter.onTouch x=337.22662
ListAdapter.onTouch x=322.623
ListAdapter.onTouch x=300.71747
ListAdapter.onTouch x=271.99695
ListAdapter.onTouch x=230.13315
ListAdapter.onTouch x=3.2896347
ListAdapter.onTouch x=-44.902443(negative)
ListAdapter.onTouch x=-75.08333(negative)
ListAdapter.onTouch x=-75.08333(negative)

-- 

3. Touch Calibration in Android 2.1

4. Exposing data to third-party apps in a synchronous call?

5. notifying that the dawvik vm has crashed

6. trying to send an MMS causes an ActivityNotFoundException to be thrown...

7. want to send an e-mail...