aframevr / aframevr/aframe-inspector
sliders should account for min/max values for calculating step/speed when dragging
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 690
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
Trying to drag geometry.thetaLength which can be 0 to 360. When I try to drag the value, the most I can do is like 5 degrees at a time.
Editor perhaps should know that the max is 360 to calculate how fast the slider should change the value.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by tracing the editor's slider-drag handling for geometry.thetaLength, then identify how its current step or speed is calculated. Done means dragging a 0–360 value allows useful movement across the full range rather than only about 5 degrees at a time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100