Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add option to allow track judging to use a different switching method #193

Open
Tracked by #167
MichaelZhao21 opened this issue Oct 30, 2024 · 0 comments
Open
Tracked by #167

Add option to allow track judging to use a different switching method #193

MichaelZhao21 opened this issue Oct 30, 2024 · 0 comments
Labels
A: Backend A task that concerns backend development A: Frontend A task that concerns frontend development difficult Issue that is relatively harder to fix high priority Issue that should be handled first new feature New feature or request

Comments

@MichaelZhao21
Copy link
Contributor

MichaelZhao21 commented Oct 30, 2024 •
edited
Loading

Currently, track judging does NOT allow for a separate switching method (auto vs manual). I would like this to be an option. Right now, the Options object has a field called "MainGroup" that is of type "GroupSwitchOps". This should easily abstract the functionality to this struct, and you can just make a copy of this main group attribute to something like "TrackGroup". The annoying part is adding a bunch of logic everywhere to check for the two and also add it all to the settings page.
@MichaelZhao21 MichaelZhao21 mentioned this issue Oct 30, 2024
Closed
54 tasks
@MichaelZhao21 MichaelZhao21 changed the title Add another set of option fields (specifically for tracks) for auto/manual switching and the projects to see before switching if auto Add option to allow track judging to use a different switching method Oct 30, 2024
@MichaelZhao21 MichaelZhao21 added new feature New feature or request high priority Issue that should be handled first A: Frontend A task that concerns frontend development A: Backend A task that concerns backend development difficult Issue that is relatively harder to fix labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A: Backend A task that concerns backend development A: Frontend A task that concerns frontend development difficult Issue that is relatively harder to fix high priority Issue that should be handled first new feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MichaelZhao21