Fix #631: Add MouseEvent and KeyEvent reference documentation #632
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.
Fixes Issue #631
This PR completely resolves the missing MouseEvent and KeyEvent reference documentation issue by adding comprehensive class references, updating all related function documentation, and providing practical examples.
Problem Summary
The Processing website was missing reference pages for
MouseEvent
andKeyEvent
classes. Users could see methods likemousePressed(event)
andkeyPressed(event)
in function signatures but had no documentation about:Solution Implemented
New Class References Created
Enhanced Function Documentation
Updated 8 core functions to include event parameter documentation:
mousePressed()
,mouseReleased()
,mouseClicked()
mouseMoved()
,mouseDragged()
,mouseWheel()
keyPressed()
,keyReleased()
,keyTyped()
Comprehensive Examples Added
Created 6 new example files demonstrating:
Files Added/Modified
New Files (10):