search

iwannabebetter / transitdatafeeder

Automatically exported from code.google.com/p/transitdatafeeder
0 stars 0 forks source link

Inputted values are not saved when editing frequency records #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Navigate to trip view (that shows stop times)
2. Change existing frequency record(s)
3. Click "Save"

What is the expected output? What do you see instead?
Frequency records inputs should be saved.  However, this data is not saved 
accurately.  Specifically, the minutes field for the stop time defaults to :00 
min.  The end time hours value match the last inputted start time hours value.

This screencast shows the behavior:
http://screencast.com/t/ZDg0NTEzMG

The expected output is that values should be saved as they are inputted.

Original issue reported on code.google.com by aaron%tr...@gtempaccount.com on 30 Aug 2010 at 7:31

GoogleCodeExporter commented 9 years ago 
Seems to still be an issue. We've been using a small shell script to make the 
adjustment manually, which is a pain.

Original comment by rypal...@gmail.com on 24 Nov 2012 at 2:18

Attachments: