Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
bad handling of bool's
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
you have parameters that use nk_bool, like for the nk_input_button, however you are handling those as int's instead... and in some places even comparing against "true" if (down==1 && ...) ... which is a bug and should be if (down && ...) (for the click on button release) and similar logic for the dragging of move/size)
so passing anything but 1 to that to cause those to fail.
Contributor guide
Research direction
Search the repository for nk_input_button, nk_bool, and comparisons against 1 or true, then inspect the related button-release and move/size dragging logic. Confirm that boolean values other than 1 are handled correctly and validate the affected input behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100