On Fri, Jan 14, 2011 at 6:29 PM, Indicator Veritatis <[email protected]>wrote:
> But be that as it may, I believe the reason he will not considers yours a > solution is that if his application is installed but not running, or if for > any reason it is not registered to handle the Intent, then no, it will not > "catch that URI" when the users browses to that link using the phone's HTTP > browser (whether that is Google's, Dolphin's or whatever). > Even if the user's app is not running, it will be an option to launch the intent. If it's not, it's because the OP himself has not set up his filters correctly or the user has already explicitly set the browser to handle it by default, which means they were presented with the option at some point. > Or perhaps he does not trust the built in browser to let his application > handle the Intent first: > There is no "first", AFAIK. It's on option to the user. > it always has been a little mysterious to a lot of us that sometimes, we > click on a link and it immediately uses the current browser, but sometimes > we get the pop-up asking us which application to use on that link. > If you have a default or only one thing to handle the intent, that gets used. If you have multiple options and no default, you get a choice. If you install a new app that can handle the intent, the default is cleared. Also, on my Nexus, the default seems to be cleared on a reboot. Not sure if that's a bug. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
