From: David B. <dav...@gm...> - 2010-07-02 01:28:28
|
Hi Brendan, >> I did recently notice that input bug in TuxType; I wasn't sure whether >> it was only in my branch, because AFAIK the library doesn't have >> anything input-related, and if it does, it's certainly not being used. >> The source code hasn't really changed much at all, TBH. Oh, well, more >> fun to debug. Any progress figuring out what the deal is with keyboard input in the tuxtype commonification branch? I've been looking at it for the last couple hours with some debugging printf()s, and something really baffling is going on here. In the "while (SDL_PollEvent(&event))" loop at line 255, no keydown events get received for presses of regular letter keys, punctuation, or anything else *except* Esc and F10, which work correctly. It isn't even a case of the events having the wrong Unicode value - they don't get picked up at all. I am at a complete loss for what might be going on here. The master branch works fine. So, unless you have been able to figure something out, I think we may need to start the "commonification" branch of tuxtype over with a much smaller divergence from master. Maybe just link in libt4k without actually calling any libt4k functions, for starters, then migrate one function at a time to libt4k. Also, I wonder if the preprocessor renaming might be triggering some unexpected side effects. Perhaps, if we see that a "#define foo_bar T4K_foo_bar" creates a bug, we could instead go back and manually put in the T4K's until we see when the bug occurs. Anyway, good work overall! David |