openframeworks / openframeworks/openFrameworks
New window drawing refresh proposal
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
I'm not happy with the cpu usage of an OF based application. I made a lot of test and it seems related to the drawing which is call regularly and can be changed using ofSetFrameRate()
I want to propose another way to refresh the window but It changes a lot of things so before starting, I'd like to know your opinion:
My idea is to only call ofNotifyEvent() when it's needed. The application ask for a refresh and the ofNotifyDraw() start aggregating requests until a timeout. It will allows to reduce "idle" CPU consumption but it also implies some modifications on the application side so let me know of you think this is a viable solution.
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 reading the window drawing and event flow around ofSetFrameRate(), ofNotifyEvent(), and ofNotifyDraw(). The issue proposes aggregating refresh requests until a timeout, but does not name files, tests, or a settled design; completion criteria would need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100