On Feb 17, 8:32 am, Bruce Tomlin <bruce#fanboy....@127.0.0.1> wrote:
> In article
> <168481b2-7634-44e2-8db7-390b3b2d1... RemoveThis @e25g2000prg.googlegroups.com>,
>
> littlesures... RemoveThis @gmail.com wrote:
> > When the initial dashboard loads, my USB mouse LED lights up and then
> > goes out. This also happens when I try to load MAMEoX, and the mouse
> > does not seem to work in either application. BUT, when I load XBMC,
> > the cursor appears and it works fine.
>
> The mouse lighting up means that the USB bus was reset, but then it
> going off means that it wasn't probed for, probably because the program
> doesn't have mouse support.
So from my observations so far, I am assuming that the XBOX does a USB
reset every time it loads Evolution, XBMC, MAMEoX, etc. And also that,
since the mouse LED turns off once Evolution and MAMEoX are loaded,
they are not supported.
What I don't understand is: shouldn't the dashboard support all of the
possible input types, since it loads first? I would think that the
applications loaded after the dashboard would all need to use the
initial configuration for all input handling. Since XBMC definitely
supports the mouse (and maybe other USB devices, for that matter), I
can't see why the others wouldn't be the same.
If I wanted to enable USB mice in other apps, would it be a question
of changing configurations, or would I need to rebuild each specific
application?
>> Stay informed about: Mouse support in MAMEoX (MAME for XBOX).