Figured this one out... along with overriding onSearchRequested(), I'm
also overriding startSearch() and inserting the required app data in
the 2 activities where I need it if it's not there and local search is
specified.  It may be redundant but, at the same time, logic suggests
that the default key handler in android.app.Activity should call
onSearchRequested() in the first place for local searching, in case
it's overridden.  Oops :-)

On May 1, 7:27 pm, Brian Smith <[email protected]> wrote:
> When implementing search in my application, I'm including some search
> context info depending on the activity where search is invoked.  In
> one of those, I'd like to implement type-to-search as well, but the
> standard method of adding search context info doesn't work in that
> case... the onSearchRequested() method in the activity is never
> called.
>
> Is there any way to include search context info in a type-to-search
> invocation, or am I stuck with only the Search key and menu option?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to