openframeworks / openframeworks/openFrameworks
ofAppEGLWindow - cursor texture is subject to gl transformations in some cases
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
On the Raspberry Pi (which uses ofAppEGLWindow) ...
If matrix transformation calls (e.g. ofRotate, ofTranslate) are not wrapped in a ofPushMatrix() and an ofPopMatrix(), the home-brew cursor texture will become subject to the global transformation stack.
@arturoc got any ideas? I think this may have something to do with not pushing the default shader each pass on the Pi.
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 locating the ofAppEGLWindow implementation and trace how the home-brew cursor texture is drawn after ofRotate or ofTranslate calls. Compare the cursor rendering with and without ofPushMatrix() and ofPopMatrix(), then investigate whether the default shader state is restored on each pass. Done means global transformations no longer affect the cursor on Raspberry Pi.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, raspberry-pi
- Domain
- computer-graphics, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100