Robert Winkler 36a8d2a5ad Fix issue 548 ... The issue was introduced in the fix for 416 (commit 8559aeb). The original problem was (backspace and arrows moving too fast) is not a nuklear problem but a GLFW problem. Because of the way nuklear handles input (it must be between input_begin and end), the key callback method GLFW offers is not an option. So we have to use glfwGetKey() which returns the current state of a key not whether it was just pressed or released, so nuklear acts like it was pressed every single frame, hence the "too fast" problem. The fix checks for state change and discards the event if there was no change. This kills key repeat behavior (for named keys) on *all* platforms which makes deleting or arrowing inconvenient. Since there's no way to fix the shortcomings of a callback vs event based input API, my "fix" just makes the original fix conditional on a macro NK_KEYSTATE_BASED_INPUT		2018-10-30 00:43:01 -07:00
..
main.c	Fix issue 548	2018-10-30 00:43:01 -07:00
Makefile	TRAVIS: include demo windows and activate warnings	2018-01-02 08:26:29 +01:00
nuklear_glfw_gl3.h	demos: fix typo (clipbard --> clipboard)	2018-09-15 06:52:10 +02:00