You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Startup ovscouter with no argument and hability to fill the teams & lineups on start
Add setter calls to setter action on reception
Add ball trajectories to court module
Playback the video at more or less than x1 speed
Button to display list of attack codes tble / plot
add set scores to scoreboard overlay
user manual
allow user to define the court reference on startup if they don't provide it
allow the user to save the court reference into the video file, if it's all running locally
Have the switch serve button next to the court module
When serve/attack end point is out of the court, automatically propose serve/attack error
Display score / set number somewhere? (not sure exactly where would be ideal...)
support remote videos (maybe including Youtube?)
add a demo function with bundled so that it can be tried easily
refine the theme, once the UI design is a bit more settled
ability to specify prior information (dvw files, or a tibble of plays data)
attack error type (in net, out long, out side, etc)
don't allow setter dumps on third contact in reception phase
option to scout without attack codes (either just the player and start location, or maybe with tempo as well)
plotting the ball path on the court diagram causes that plot to be re-rendered after each action, which slows things down noticeably. Rewrite the court diagram module to use base graphics, which will be a lot faster (or some other solution)
option to restart from recovery rds file
ability to set options (e.g. scoreboard, showing ball paths on court diagram) from within the UI
rotation buttons when entering lineup so that the existing lineup can be rotated plus/minus one position
plays table optionally be shown as a plain-language interpretation of each contact, rather than dvw codes
The text was updated successfully, but these errors were encountered:
As of 42f9ddb it should be possible to start with just dv_create(teams = c("Home team name", "Visiting team name")) and enter everything else in the app. Not properly tested though.
Have done the serve error proposal when the ball is out of court, but not (yet) attacks, because not sure whether ball off hands (and either out, or dug from out of bounds) will be more common than the ball directly out (attack error). Needs discussion/thought.
The text was updated successfully, but these errors were encountered: