The truth about the e200 button problems.

Ok, I finally got my device back from Casio, and I have done some experimenting with it. Ok, here is what I have found when it comes to the dpad. In the os apps(i.e. scrolling through menus and in Word)it you can switch from one direction to another, and back again, and it function correctly. In games however, when you push, well, let me give an example....
You are playing Mario 3 in an NES emu, and you are goining right. Now, if you press up and then let go of right, you will keep going right. If you press left and then let go of right, you will stop dead in your tracks. Also, the scroll whell apears to function as if you pushed the up and down buttons in respect to the action they take, and to the dpad problem (in which case, pushing up on the scroll whell, causing the same up senario listed above).
Now on to the buttons.
Ok, this is a tricky one. Let's use the mario example from above. You push the B button, as any mario player would because you always want to be running. Now, you hit the A button (while holding the B button). You just up for the full height of your jump, and then you land. So, you think, what about that 2 button problem. You then push the A button again, and nothing happens (you are still holding the B button). For what ever reason, you push the up button (and then let go), and then hit the A button. You jump. This phenamina, which from now on will be called the muffin phenomina, works for all directional buttons, including the scroller and the action button. Now, it is not untill you let go of one of these magic buttons that you can once again use the two button combination.
So, what is my thought on this whole thing? Well, I say it is a gapi problem. Does quake use the GAPI for defining hardware buttons? If not, I can do further testing in it with that.
You are playing Mario 3 in an NES emu, and you are goining right. Now, if you press up and then let go of right, you will keep going right. If you press left and then let go of right, you will stop dead in your tracks. Also, the scroll whell apears to function as if you pushed the up and down buttons in respect to the action they take, and to the dpad problem (in which case, pushing up on the scroll whell, causing the same up senario listed above).
Now on to the buttons.
Ok, this is a tricky one. Let's use the mario example from above. You push the B button, as any mario player would because you always want to be running. Now, you hit the A button (while holding the B button). You just up for the full height of your jump, and then you land. So, you think, what about that 2 button problem. You then push the A button again, and nothing happens (you are still holding the B button). For what ever reason, you push the up button (and then let go), and then hit the A button. You jump. This phenamina, which from now on will be called the muffin phenomina, works for all directional buttons, including the scroller and the action button. Now, it is not untill you let go of one of these magic buttons that you can once again use the two button combination.
So, what is my thought on this whole thing? Well, I say it is a gapi problem. Does quake use the GAPI for defining hardware buttons? If not, I can do further testing in it with that.