"End call" button and "Redial" button are in the same location

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Be ready to end a call with someone
2. Prepare to hit the "X" to end the call
3. Other end hangs up first

What is the expected output? What do you see instead?
Before realizing that the other end has hung up, the "Redial" button is pressed 
instead of the end call button. This has happened to me twice already. :(

What version of the product are you using? On what operating system?
1.0.1

Please provide any additional information below.
Not sure what would solve this without uglying up the UI. Maybe a couple second 
delay before the redial button can be pushed? That way you could still 
accidentally hit the button, and you would think that you ended it yourself. No 
harm done.

Original issue reported on code.google.com by sevent...@gmail.com on 21 Feb 2011 at 6:32

[GoogleCodeExporter]

I have no idea where the ticket is, but over a year ago I suggested a delay of 
3 sec after end of call before the hangup button becomes the redial button. 
Additionally, if the setting to close call window at end of call is on, then 
button should never become redial. Nothing has been done to address this 
seriously annoying issue. I accidentally redial a few times a week.

A related bug is that once it is dialing, it doesn't become a hangup button 
until the call connected, so you can't help but annoy the other party. If you 
close the window while its dialing, the call goes on with no way to stop it 
short of closing telephone.app! If the call was one I initiated using Google 
Voice, meaning google called me and then the other party, hitting redial calls 
my own number and closing the window proceeds to leave a 3 minute voicemail for 
myself. ARGH!

Original comment by mre...@gmail.com on 10 Mar 2011 at 12:56

[GoogleCodeExporter]

Hmmm that's annoying... If I get some time this weekend I might just look into 
this and fix it myself.

Original comment by sevent...@gmail.com on 10 Mar 2011 at 3:15

[GoogleCodeExporter]

There is a delay when redial button changes from disabled to enabled state when 
remote party ends the call. Added it long time ago, after the first issue. 
Maybe I should increase that delay.

Original comment by eofs...@gmail.com on 10 Mar 2011 at 11:41

[GoogleCodeExporter]

Not it is set to 1 second.

// Redial button re-enable delay.
static const NSTimeInterval kRedialButtonReenableTime = 1.0;

Original comment by eofs...@gmail.com on 10 Mar 2011 at 11:44

[GoogleCodeExporter]

Not = Now.

Original comment by eofs...@gmail.com on 10 Mar 2011 at 11:54

[GoogleCodeExporter]

This is so dumb, why does google voice put the Redial button where the END call 
button is?  I go to click on end call, but the other line hangs up at the same 
time and I end up calling them for no reason.  This is such an obvious design 
flaw, yet google hasn't changed the button or added a delay.. 

Original comment by i...@carbonfiberhoods.com on 19 Apr 2012 at 9:11

[GoogleCodeExporter]

This isn't Google's project.

Original comment by m...@stith.me on 20 Apr 2012 at 4:00