This post is a direct follow-up to my post Saturday about the Enter key bug on Mac OS X. After another user on a PowerBook reported the same problem, I began thinking about keyboards on laptops. Using one of the small wxWidgets demo applications, the tester was able to relay to me that the Enter key was not producing the key event corresponding to Enter, but to the Numpad Enter key. Since the Numpad Enter has a different keycode, BitWise wasn't recognizing it. After investigating for hours, I couldn't find a good explanation for this, and decided just to hack the key event generated by wxWidgets to morph Numpad Enter events into Enter events.
Unfortunately, this isn't perfect. Shift and Ctrl Enter won't be recognized for entering newlines. I also still have no idea why this mapping changed between wxWidgets 2.6.3 and 2.7, though the key handling was "improved." There's also no good explanation why the only models experiencing this problem were PowerBooks. It's almost like there is some default keyboard mapping that makes PowerBooks handle these keys differently.
In the meantime, a new version of 1.7.1 was uploaded yesterday (Sunday) to incorporate this fix. Perhaps as time goes on, more information will become available and will help lead to a more permament solution. The software world isn't perfect, unfortunately, but the good part is that sometimes all it takes is a not-so-clever hack to make things usable again.
Anyone with any more information about the Enter bug is welcome to add to our forum thread. Any more clues would be greatly appreciated!