Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
nk_edit_* and nk_property_* both get cursor focus when used next to each other
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
This was originally mentioned at the very bottom of https://github.com/Immediate-Mode-UI/Nuklear/pull/900#issuecomment-3924069488, I've speculated that not using `#` for nk_property prevents it from hashing correctly (https://github.com/Immediate-Mode-UI/Nuklear/pull/900#discussion_r2825416853) but I already tried it in https://github.com/Immediate-Mode-UI/Nuklear/commit/ff2ff046aacc20ba060122c0d1067797037c7a87 and the problem is still there. This is a bug withing library and there is one specific place in demo/common/overview.c that can reproduce 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 with the reproduction in demo/common/overview.c, placing nk_edit_* and nk_property_* next to each other as described. Review the linked pull request discussion and referenced commit, then trace how these widgets handle cursor focus and hashing. Done means the adjacent widgets no longer both receive cursor focus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100