Let me give an example of a different kind of app.. I have already
read the main thread where this touchscreen consuming CPU issue is
discussed...
Now I have a game which is completely single threaded..
for rendering I use a timer and use handler.post and call invalidate/
postInvalidate of a View
Let me give an example of a different kind of app.. I have already
read the main thread where this touchscreen consuming CPU issue is
discussed...
Now I have a game which is completely single threaded..
for rendering I use a timer and use handler.post and call invalidate/
postInvalidate of a View
In general, you shouldn't be starting an activity at all passed on
movements. Probably not on downs either. Only on ups. And at that point,
if you want to abort the operation based on movement, just look at how far
the up event x and y is away from the original down event.
On Mon, Apr 13, 2009
can u give some sample code, technical details about that touch
thresholding, I have been trying to implement and I am missing
important events
On Apr 13, 7:07 am, Ralf wrote:
> On Sun, Apr 12, 2009 at 6:28 PM, Todd Sjolander
> wrote:
>
> > Marco, your hunch was right. I was somehow creating
Fwiw, "adb shell dumpsys activity" is very useful to see what is going on in
your activity stack. Also the is a log statement for each call to
startActivity().
On Sun, Apr 12, 2009 at 6:28 PM, Todd Sjolander wrote:
>
> Marco, your hunch was right. I was somehow creating multiple copies
> of Act
On Sun, Apr 12, 2009 at 6:28 PM, Todd Sjolander wrote:
>
> Marco, your hunch was right. I was somehow creating multiple copies
> of Activity C. In case anyone can benefit from this, let me explain
> how it went wrong.
>
> I implemented onTouch() in Activity B, which would create an Intent
> for
On Sun, Apr 12, 2009 at 6:28 PM, Todd Sjolander wrote:
>
> Marco, your hunch was right. I was somehow creating multiple copies
> of Activity C. In case anyone can benefit from this, let me explain
> how it went wrong.
>
> I implemented onTouch() in Activity B, which would create an Intent
> for
Marco, your hunch was right. I was somehow creating multiple copies
of Activity C. In case anyone can benefit from this, let me explain
how it went wrong.
I implemented onTouch() in Activity B, which would create an Intent
for Activity C, and then call startActivity(). For some reason,
onTouch
On Sun, Apr 12, 2009 at 1:05 PM, Jon Colverson wrote:
>
> On Apr 12, 1:07 pm, Todd Sjolander wrote:
>> hardware back button. In the emulator, it takes two presses of the
>> back button in order to close Activity C and come back to B. On a G1,
>> it takes 3 or 4 presses.
>
> When you're testing
On Apr 12, 1:07 pm, Todd Sjolander wrote:
> hardware back button. In the emulator, it takes two presses of the
> back button in order to close Activity C and come back to B. On a G1,
> it takes 3 or 4 presses.
When you're testing, do you clear the activity history (by going back
to the home sc
Are you sure you don't have several instances of activity C, and each
press of the back button exits one until you finally get back to
activity B? Try printing "this" in C.onDestroy() to make sure.
On Sun, Apr 12, 2009 at 5:07 AM, Todd Sjolander wrote:
>
> Hello,
> I've got an application that
11 matches
Mail list logo
