Hello, thanks for the info.
Am Mo, 5.07.2010, 16:00 schrieb Vincent Sanders: > There is a bug in the current implementation of the framebuffer > toolkit with respect to input widgets in that they do not actually use > the keycode->ucs translation table. > If you spot any more issues with the framebuffer toolkit please let me > know as I am currently in the middle of a major refactor of this code. When I enter an key which is not recognized ( or not know ) by the keyboard driver, resulting in an 0 char ... the 0 is inserted into the URL String and no other input can be made. 0 keycodes shouldn't be processed, as it seems. > Please feel free to check out my fbtk-rework branch to see if the > refactor has solved your issue. I'll have a look. -- Greets, Ole
