Weird Happ trackball issues

[FunWithFire]

First off, I am using the USB Happ 3 inch trackball with the three buttons hooked to it.
I put together a travel arcade panel, and while setting everything up, I had an additional mouse and keyboard hooked up to it. I finalized everything last night so I disconnected the mouse and keyboard, brought it home (I had been building it at work) and fired it up at the house. All of the trackball games were not working, and when I went into the settings, the trackball x and y were set as 'n/a.' I guess when I disconnected the mouse, the trackball (which had initially been set as mouse 2) now became mouse 1 so the computer could not find a mouse 2 and just undid the setting. After I realized this I redid the settings, and the trackball worked fine.
The problem I am having is this: the three buttons that connect to the trackball had been set as tab, exit, and pause. After I redid the settings for these three buttons, tab and exit worked, but when I hit the pause button, I cannot unpause it. This worked fine before when the trackball was mouse 2. In fact, none of the three buttons would work after hitting the pause connected to the trackball. But if I hit the actual Esc key on the keyboard, the game would exit. The trackball tab and exit work fine, unless I have already hit the pause button.
For now I have undone the pause key. This panel is going to be a gift tomorrow, so I have only a tab and exit on the trackball now. I was just curious if this is something someone else has experienced. Sorry about the long post.

[u_rebelscum]

The problem I am having is this: the three buttons that connect to the trackball had been set as tab, exit, and pause.... none of the three buttons would work after hitting the pause connected to the trackball.

Do you mean that you set the mouse buttons to mame's "UI Configure" (usually tab), "UI Cancel" (usually esc), and "Pause" (usually P)?  If so, you can't get out of mame because mame stops looking at the mouse inputs when paused.

The reason I ask is you said:

This worked fine before when the trackball was mouse 2.

I've never heard of this before.  I'll have to test it and see if mouse 2+ (or some other reason) are treated differently than mouse 1.