Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
nuklear_gdip: nk_edit_focus Vs. keyboard focus
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
I created a small GUI with several windows. Each window has 2 or more string input fields. I also added a small feature to navigate between these fields using TAB and Shift-TAB. This works perfectly fine.
But the input fields only get the keyboard focus if the mouse hovers over the corresponding window.
Is this intended? Is there a way around this behaviour?
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
Reproduce the reported setup in the nuklear_gdip backend with several windows and string inputs, including TAB and Shift-TAB navigation. Compare nk_edit_focus with keyboard focus and determine whether the hover requirement is intended; done when the behavior is clarified or a confirmed way to avoid it is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100