I would avoid disabling the call button. I think users should still be able to enter USSD codes during a call, so the call button needs to be enabled all the time. Also, other protocols like sip might allow this use case (call another number while the current call isn't fully active). There is another use case that we currently don't support but also needs the call button enabled, which is pressing the call button when no number was entered to fill the entry with the last called number.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1404301 Title: shouldn't allow dialing second call while first call still in progress Status in Dialer app for Ubuntu Touch: New Status in dialer-app package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Bug description: rtm build 184 on krillin Steps to reproduce: - open dialer - make a call to number 1 - while the first call is ringing but not yet answered, immediately either switch to keypad and dial another number (or press the contacts button and select a contact's number) and press the Call button Expected results: - both calls should be placed and the view should switch to the multiple calls view showing both as "calling.." OR - if this is not technically possible, then the UI for placing a second call (keypad and contacts buttons) should be disabled until the first call is active Actual results: - the second call is never placed and the UI never switches from the live call view of Call 1 To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1404301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
