search

FIRST-Tech-Challenge / scorekeeper

FIRST Tech Challenge Live Scorekeeper Software
87 stars 21 forks source link

Suggest separating the "Start" and "Abort" match button positions #744

Open Cannongeorge opened 1 week ago

Cannongeorge commented 1 week ago

Is your feature request related to a problem? Please describe. When starting a new match, immediatley upon starting a match the underlying "Start Match" button turns into an "Abort Match" button. When using foreign scorekeeper computers with unfamilier track wheels, mice, or "nibs" I'm always terrified of key bounce and accidently triggering an "Abort" when I don't want to.

Describe the solution you'd like Immediatley upon successfully starting a new match, "Grey out" the start match button and illuminate a new pop-up, an "Abort Match" button, to be located immediatley to the right of the previously mentioned "Start Match" button.

Describe alternatives you've considered Upon successfully starting a new match, carefully "nudging" the mouse away from the (newly defined) "Abort" pad location. But when using "nibs" or fingerpads on foreign machines I'm still terrified of accidentially introducing an "abort" when I don't want to!

Additional context If I travel to other meets I cannot always use the laptop computer that I am used to for match control.

timtim17 commented 5 days ago

For what it's worth, there is a popup and confirmation before the match is actually aborted.

Cannongeorge commented 4 days ago

Thank you for confirming that! I stand corrected thus this issue not as concerning as I thought. George

On Tue, Oct 15, 2024 at 1:15 AM Austin Jenchi @.***> wrote:

For what it's worth, there is a popup and confirmation before the match is actually aborted.

— Reply to this email directly, view it on GitHub https://github.com/FIRST-Tech-Challenge/scorekeeper/issues/744#issuecomment-2413197067, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMBZY255RKHJ43MOVTYPA2DZ3TFITAVCNFSM6AAAAABP2ZAOPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGE4TOMBWG4 . You are receiving this because you authored the thread.Message ID: @.***>