Clarify FloatInput value/value_thottled behavior in docs #5249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thought I'd tweak this documentation that read a little funny to me when I was raising issue 5205. I think the word spinner threw me which I interpreted as busy spinner but maybe that meant spinbox.
I did some testing and found the value and value_throttled behaved seemingly identically in terms of updates. Also couldn't get the mouse wheel to change the value at all as the documentation implies it should.
Happy to have this PR rejected if I'm being too verbose or am writing too inconsistently with the other docs - I'm trying to slowly wrap my head around the preferred writing style and constraints.
Took the liberty of tweaking the .gitignore too as I was using PyCharm at the time and saw its config wasn't ignored while VS Code's was.