Skip to content

Add multi-counter input for fuel tracking#102

Merged
tytremblay merged 4 commits intomainfrom
fuel-counter-input
Mar 5, 2026
Merged

Add multi-counter input for fuel tracking#102
tytremblay merged 4 commits intomainfrom
fuel-counter-input

Conversation

@luanzeba
Copy link
Collaborator

@luanzeba luanzeba commented Mar 5, 2026

Came out of a discussion on how to more easily measure fuel scored during a match. Counting individual pieces is way too fast, so this adds a new multi-counter input type with +1/+5/+10 (and their negatives) for ballpark estimates.

Added it to both auto and teleop in the config. The running tally makes it easy to confirm taps registered.

Tested it on Android tablet to make sure it works!

Demo below 👇

fuel-counter-demo.MP4

luanzeba added 3 commits March 5, 2026 15:02
New input with +1/+5/+10 and -1/-5/-10 buttons for quick ballpark
counting. Displays a running tally so scouts can confirm button
presses took effect. Value is floored at 0.

Uses active: instead of hover: for press feedback to avoid sticky
highlight on touch devices.
Adds multi-counter fields at the top of both Autonomous and Teleop
sections for tracking approximate fuel scored. Bumps store version
to invalidate cached config.
Follows existing input type documentation pattern with config
example, properties, usage guide, data format, FRC scouting
examples, and best practices.
@github-actions
Copy link

github-actions bot commented Mar 5, 2026

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://FRC2713.github.io/QRScout/pr-preview/pr-102/

Built to branch gh-pages at 2026-03-05 20:18 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

import { MultiCounterInputData } from './BaseInputProps';
import { ConfigurableInputProps } from './ConfigurableInput';

const INCREMENTS = [1, 5, 10];
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] we could probably make this configurable in a future MR. These increments make sense for this year, but next year there might be something that prefers to count by 3s

@tytremblay tytremblay merged commit 0642e00 into main Mar 5, 2026
1 check passed
luanzeba added a commit that referenced this pull request Mar 6, 2026
Replaced by the multi-counter input in #102.
luanzeba added a commit that referenced this pull request Mar 6, 2026
Replaced by the multi-counter input in #102.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants