Add `strokeWeight` to reference in the reference of `point_`
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 60/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- json
- Domain
- documentation
Research direction
Open content/references/translations/en/processing/point_.json at the referenced description and related fields. Compare the proposed wording and related reference entries with nearby reference files, then update the point_ content; it is done when strokeWeight is correctly emphasized and linked in the rendered reference.
Written by the indexing model from the issue text.
Description
Select the type of content error.
Other content error (please specify)
Section
Reference
Location of the error
Describe the error
I don't know if it is intended, but it would be nice to make strokeWeight() function bold in description section and add strokeWeight() function in related section
Suggested correction
- Change
descriptionto:
"description": "Draws a point, a coordinate in space at the dimension of one pixel. The first\n parameter is the horizontal value for the point, the second value is the\n vertical value for the point, and the optional third value is the depth\n value. Drawing this shape in 3D with the <b>z</b> parameter requires the P3D\n parameter in combination with <b>size()</b> as shown in the above example.\n <br/>\n <br/>\n Use <b>stroke()</b> to set the color of a <b>point()</b>. <br/>\n <br/>\n Point appears round with the default <b>strokeCap(ROUND)</b> and square with\n <b>strokeCap(PROJECT)</b>. Points are invisible with <b>strokeCap(SQUARE)</b>\n (no cap). <br/>\n <br/>\n Using point() with <b>strokeWeight(1)</b> or smaller may draw nothing to the screen,\n depending on the graphics settings of the computer. Workarounds include\n setting the pixel using <b>set()</s> or drawing the point using either\n <b>circle()</b> or <b>square()</b>.",
- Change
relatedto:
"related": ["stroke_", "strokeWeight_"],
Language
json
Screenshots or references
No response
Additional context
No response
- Dominant language
- MDX
- Stars
- 90
- Forks
- 122
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 3
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.
More from processing/processing-website
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
processing/processing-website#703 ·
-
Good First Issue Help Wanted Reference
Difficulty 1/5 Under an hour Newbie friendliness 90/100
processing/processing-website#698 · 5 comments · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
processing/processing-website#681 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
processing/processing-website#646 · 3 comments ·
-
Tutorials
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/processing-website#358 · 2 comments ·
All issues in processing/processing-website
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100