processing / processing/processing4
Debugging P2D is way harder then JAVA2D
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
This has been bugging me for years.
If I have a Uncaught Exception in P2D then it always breaks here with doesn't really help.
Compared to JAVA2D which breaks where it goes wrong and also has a stacktrace that is helpfull.
I often switch from P2D to JAVA2D for debugging, but this is sadly not always possible. And in projects with shaders invovled it is not possible at all.
I could provide more info but since I see so many issues locked due to a 30 day thing I'm not gonna waste more time on it.
Contributor guide
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
Start by reproducing an uncaught exception in the P2D renderer and compare where it breaks and what stack trace it produces with JAVA2D. The issue is complete when P2D identifies the failing source location and provides a useful stack trace, including for projects using shaders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100