Main > Main Forum

Buttons react when released instead of pressed

Pages: (1/2) > >>

fnord12:

I have two buttons on my cab that, instead of getting recognized when they are pressed, are recognized when they are released.  Since it's my Player 1 Start and Player 3 Start buttons, it's a minor, almost unnoticeable difference, but of course it's bugging me so I wanted to see if anyone else has experienced this.  My first thought was that I wired to the "Normally Closed" connection by accident, but that doesn't seem to be the case and the wiring and everything seems to look ok.

One thought is that since I'm using an IPac and these are the shift keys, maybe it's waiting to see if i push something else before sending a signal?  But I haven't heard anyone else running into this "problem".

Anybody run into this?  Thanks!

severdhed:

i could be wrong, but i believe the ipac shift keys don't send anything until they are released, due to the nature of a shift function

EVEGames:


--- Quote from: severdhed on September 13, 2010, 04:49:20 pm ---i could be wrong, but i believe the ipac shift keys don't send anything until they are released, due to the nature of a shift function

--- End quote ---

Exactly right, this is by design, as the IPac cannot predict whether or not you are going to use a Shift function, so it holds off on sending the normal keycode until you release the button.  If you think about it, you most likely wouldn't want your Shift button to automatically send its normal keycode every time you press it.  While in a game, it would be pretty harmless, but in the front end, it could cause headaches.

-EVEGames

Bender:

Exactly, my player one button does that because it's set as the shift key on my MiniPac

haven't run into any problems with it interfering in any way have you?

cmoses:

I have the MiniPac as well and my Player 1 button does the same thing.  I bugged me when I was first setting up the control panel, swapped buttons, microswitches, checked wiring, etc.  Eventually just let it be becuase it did not affect anything.  I never thought about it being the Shift function until this post.  It makes total sense now.

Never had an issue with it, so don't let it bother you.

Pages: (1/2) > >>

Go to full version