Ticket #19 (closed task: fixed)

Opened 2 years ago

Last modified 10 months ago

Bad timecodes should be ignored

Reported by: sthiel Assigned to: sthiel
Priority: minor Milestone: milestone6
Component: UI Version:
Keywords: Cc:
Super-ticket: Reviewer:
Minutes Spent:

Description

Right now, exceptions can be thrown and all sorts of problems can happen. I'd like to make it so that a) non-numeric data can't be entered b) invalid times (times outside the duration) can't be entered.

If pseudo-correct times, like 68 seconds, instead of 1:08 are entered, they should be normalized immediately, before things actually trigger lost-focus events (or something should catch that first).

Change History

04/13/07 12:47:12 changed by sthiel

  • milestone changed from milestone1 to milestone2.

-I ran out of time, so I've moved this to milestone2

04/27/07 18:25:50 changed by sthiel

  • minutes_worked changed.
  • milestone changed from milestone2 to milestone3.

-Gotta move it to milestone3, I'm running too far behind.

03/07/08 09:45:08 changed by sthiel

  • reviewer changed.
  • super_ticket changed.
  • milestone changed from milestone3 to milestone6.

mostly implemented

03/08/08 11:37:34 changed by sthiel

  • status changed from new to closed.
  • resolution set to fixed.

-Fixed in 171 172 --Time for this is given in #21

03/08/08 11:39:20 changed by sthiel

doesn't automatically reformat weird times like 68 seconds to 1:08 make a new ticket for that later if people request it... as soon as it starts playing, that happens now anyway.