Proposal Action Buttons: start and stop

[a-tze]

Issue migrated from trac ticket # 73

component: webapp | priority: major

2014-07-06 13:38:37: @a-tze created the issue

---

For Recording tickets in states scheduled resp. recording there could be action buttons in the ticket list with following semantics:

-* start button** -for tickets in "scheduled" or "recording" -ask for something like "started [.....] minutes ago", maybe with an additional "now"-button -set Fahrplan.Starttime to current time minus value entered above -set Record.StartPadding to a low value, like 60

-* stop button** -for tickets in state "recording" -ask for something like "ended [.....] minutes ago", maybe with an additional "now"-button -set Fahrplan.Duration to current time minus value entered above - Fahrplan.Starttime -set Record.EndPadding to a low value, like 60 -do NOT change ticket state

this could save time and confusion in the cutting process at some events, or it may even be possible that cutting is unnecessary at all.

[a-tze]

2014-07-12 11:05:10: @jjeising changed status from new to accepted

[a-tze]

2014-07-12 11:05:10: @jjeising changed owner from ** to texec

[a-tze]

2014-07-12 11:05:10: @jjeising commented

---

When we don't change the ticket state, isn't it counterintuitive that you can stop a recording ticket multiple times?

I suspect that starting moves a ticket to recording when in scheduled?

[a-tze]

2014-07-12 12:42:19: @a-tze commented

---

A ticket state change could be done for the "start" button.

Not changing ticket state on pressing "stop" is NOT counter-intuitive IMO, because:

• it could interfere with worker scripts
• of course you should be able to stop a recording multiple times, since it is just a time marker. Using the "last wins" pragma, you can change the time marker easily.

Maybe the names shouldn't be "start" and "stop"... but stg. like "mark in" and "mark out" is not the vocabulary of our intended audience ;)