Ignore that last idea - doesn't make sense with 5 minute increments. 
Would be way too many options. Also, I showed the changed behavior to 
my wife and it make perfect sense to her, so I'm going to commit it as 
requested.

I have this implemented locally but I'm not sure it's the most 
intuitive thing since it's hard to ensure that you really only do the 
toggle when the user expects it.



What if we instead combined the hour and minute fields into one field? 
That'd eliminate the am/pm buttons entirely, and it'd be obvious to 
the user when they were scheduling the event for.

I'll leave commenting on this to a developer that actually uses am/pm. ;)

If you are not using 24 hour time, but AM and PM, and if you have an 
event that starts in the morning and ends in the afternoon, the code 
will kick back a warning that the start date can't be later than the 
end date.  Most people that create events that have an end date that 
is numerically lower than the start date are scheduling all day 
meetings.  It would be helpful to have the javascript code take this 
into consideration and make the assumption that if you are trying to 
schedule an 8AM - 4PM meeting, that it will make the switch to PM if 
you pick 4 as your end hour.



People usually think from left to right, top to bottom, so they will 
attempt to change the hour first, get the message, then they have to 
change AM/PM and then they can put in the proper hour.  This 
enhancement would allow them to create an event without an 
interruption.  They shouldn't have to think about doing AM/PM first.



Alternative would be to put the AM/PM to the left of the hour menu, 
but thats not appealing at all.