Oh cool. I see what you're getting at. Thanks. I actually know exactly
how that happened. I originally used ACTION_CALL (and therefore had to put
CALL_PHONE in). I didn't like having it immediately dial so I switched to
ACTION_DIAL and liked the interaction a lot better that way (allowing the
user to confirm the call) but CALL_PHONE got left in as a by-product. In
evolution this process is referred to as "scaffolding" by the way, where
the evolution of feature X requires feature Y but at a later time Y fades
away leaving X looking fairly inexplicable.
Thanks.
On Wednesday, September 19, 2012 3:31:30 PM UTC-7, Mark Murphy (a Commons
Guy) wrote:
>
> On Wed, Sep 19, 2012 at 6:24 PM, Keith Wiley <kbw...@gmail.com<javascript:>>
> wrote:
> > The ability to jump to the phone dialer was a
> > specific user request (not even my idea) to enable users to tap phone
> > numbers in spread sheets and jump to the dialer app to easy calling.
>
> You do not need CALL_PHONE to use ACTION_DIAL ("jump to the dialer
> app"). You need CALL_PHONE to use ACTION_CALL.
>
> --
> Mark Murphy (a Commons Guy)
> http://commonsware.com | http://github.com/commonsguy
> http://commonsware.com/blog | http://twitter.com/commonsguy
>
> Android Training in NYC: http://marakana.com/training/android/
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
