It depends.
Usually your activity (either WaitActivity or some other activity of
your app) starts or binds to your service. The activity is the
initiator. Your service can stay around for a while.
When your activity binds to your service, the activity can call your
service and your service can ca
I assume when you say "tie/bind" here you aren't just referring to spawn
activity via intent
On Nov 11, 2010 11:03 AM, "Streets Of Boston"
wrote:
> Tie/bind your service to a visible activity (let's call it
> WaitActivity).
>
> If it is really important that user reacts immediately while your
> se
Tie/bind your service to a visible activity (let's call it
WaitActivity).
If it is really important that user reacts immediately while your
service chugs along and needs more info, the user'd better be looking
at the phone and looking at the WaitActivity.
E.g. you could show an activity (WaitActi
3 matches
Mail list logo
