Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
Is there a non-redraw mode?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
Basically I'm using this in an app that is supposed to run along side games and I don't want it causing slow downs because of it hogging resources, I'd like to know if there is a way to tell nuklear to only redraw on ui events like a mouse click and not on every frame unless a call to something like nkupdate()/nkredraw() is done
The app I'm making is this one:
https://github.com/awsdert/gasp
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 examining Nuklear's nkupdate()/nkredraw() entry points and how the linked Gasp app drives frames. Define the non-redraw behavior and its handling of UI events; the work is done when an explicit update or redraw can control rendering without requiring every frame.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100