yes, correct way to do it is with interfaces which are documented copiously ~ I just read in the developer docs that Interfaces are the correct way to avoid wait's and blocks
On Nov 2, 10:54 pm, Miles <[email protected]> wrote: > Hi, > > Is there any way to to listen for activity/application lifecycle > events without having to extend the classes? > > Reason for this is we are providing a component that needs to detect > when an activity/application is paused or resumed. And for > convenience sake we don't want the client to have to notify the > component every time activity lifecycle changes. If possible we just > want the component to hook into the lifecycle events and be informed > automatically by the android system. > > We could make the component extend Activity and let the client extend > the component, but this would be more complicated for the client. We > want to keep things simple for the client as possible even if it makes > our component more complex. > > So is there a way to hook event listeners for lifecycle events? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
