documentation for Range property "page" is incomplete

Open Beginner friendly
#12,007 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start with the linked Range documentation page, especially the page property section and the related max_value description. Verify the described clamping and scrollbar range behavior, then update the documentation so the effective maximum and grabber-length explanation are accurate and complete.

Written by the indexing model from the issue text.

Description

area:class reference bug

Your Godot version:
Godot 4

Issue description:
The documentation for Range's "page" property states simply:
Page size. Used mainly for ScrollBar. A ScrollBar's grabber length is the ScrollBar's size multiplied by page over the difference between min_value and max_value.

From my own testing I think this is misleading and incomplete. It seems page size actually alters the effective maximum value of the Range. i.e. a Range with a max_value of 100 and a page of 10 will actually be clamped to 90. That's not mentioned anywhere, not under page nor under max_value. This also makes the statement about the ScrollBar's grabber length technically inaccurate since it's actually the ratio between page and the effective range that matters (i.e. max - min - page and not simply max - min).

URL to the documentation page (if already existing):
https://docs.godotengine.org/en/stable/classes/class_range.html#class-range-property-page

Dominant language
reStructuredText
Stars
5.7k
Forks
3.8k
Avg merge
7d 14h
Merged PRs (30d)
41

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from godotengine/godot-docs

All issues in godotengine/godot-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.