[Karlson2k]

Bug trac: http://trac.xbmc.org/ticket/13146
Issue thread: http://forum.xbmc.org/showthread.php?tid=134074
iMON forum thread: http://www.soundgraph.com/forums/showthread.php?t=10536
Root of the problem: see 'Cause' in http://www.soundgraph.com/forums/faq.php...amecontrol
Pull request: https://github.com/xbmc/xbmc/pull/1111

I don't see any other solution then disabling joystick code, because any call to device enumeration with DirectInput API cause iMON disconnect/connect cycle.
Joystick code can be disabled ether after automatic detection of problematic iMON or by setting in AdvancedSettings.xml.
I suggest to start from AdvancedSetting and, when (and if) it'll be possible, add autodetection.

Additional setting is itself complete and can be used beside iMON problem.

Does anyone have other suggestions?

[WiSo]

My experience is that temporary solution live endless. Once the advance setting is in nobody will care about it anymore. I don't have any experience with imon so I just can give some pointers like checking for any imon software that is installed (if we wanna disable it for all imon setups). This can be done via the registry (see GetCrystalHDLibraryPath() in win32util.cpp) or looking for a certain dll. If there's nothing you can find I have to discuss with jmarshall if we accept the advanced setting for it.

[spiff]

my .02c;

1) we want a proper fix for the imon
2) the setting has a merit on its own and should be in-gui like the mouse one. e.g. when you want to do some emulating and don't want xbmc to listen to your frenic buttoning while smashing up zangief.

[Karlson2k]

iMON advice:

try to disable enumerating game controller in XBMC.

Source: http://www.soundgraph.com/forums/showpos...ostcount=6

Anyway i'm working on match better way of implementing this and with GUI setting instead of AdvancedSettings.

[Karlson2k]

Rewrote patch in pull request.
Reflect mouse methods to CJoystick.
Looks pretty good now.