processing / processing/processing-website
[Reference] saveFrame
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 90
- Forks
- 122
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 3
Description
Issue description
A processing.org/reference/saveFrame_.html statement seems incorrect:
// Saves each frame as screen-0001.tif, screen-0002.tif, etc.
saveFrame();
URL(s) of affected page(s)
processing.org/reference/saveFrame_.html
Proposed fix
Update processing/processing-website/content/references/examples/processing/saveFrame_/saveFrame_0.pde
from
// Saves each frame as screen-0001.tif, screen-0002.tif, etc.
saveFrame();
to
// Saves each frame as screen-0001.tif, screen-0002.tif, etc.
saveFrame("screen-####.png");
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
Open content/references/examples/processing/saveFrame_/saveFrame_0.pde and compare its saveFrame() example with the affected saveFrame reference page. Update the example so the documented filename and format match the proposed saveFrame("screen-####.png") usage; done when the reference no longer shows the incorrect statement.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100