aboutsummaryrefslogtreecommitdiff
path: root/engines/sword1
diff options
context:
space:
mode:
authorFlorian Kagerer2010-10-24 19:15:17 +0000
committerFlorian Kagerer2010-10-24 19:15:17 +0000
commit0db700a3dced67c607c9e9719ea22347612ead40 (patch)
tree90f85aaf41fe60a21be4b0d5834bb195af6ad56e /engines/sword1
parentf37252e6cfacf1a1546265ffc7895e499a2b7e54 (diff)
downloadscummvm-rg350-0db700a3dced67c607c9e9719ea22347612ead40.tar.gz
scummvm-rg350-0db700a3dced67c607c9e9719ea22347612ead40.tar.bz2
scummvm-rg350-0db700a3dced67c607c9e9719ea22347612ead40.zip
GUI/LAUNCHER: improved MIDI device selection (also #3088438)
This fixes an issue with the <default> setting in the GM and MT-32 device tabs that has caused some complaints and discussions on -devel. It might also be what bug #3088438 is about. With a <default> setting ScummVM would just use the first available MIDI device (even if this is the not really well working MT-32 emulator). This <default> setting was also indeed set by default - making it even more annoying. Now there is a new setting for both the GM and MT-32 device tabs ("Don't use GM/MT-32 music"). This will cause MIDI device detection to be skipped and the best of the other devices (Adlib etc.) to be used. This new setting is used as default. So users who haven't specified anything will get Adlib, PC Speaker etc. (if supported by the engine) even if the engine prefers Midi. There is a new "Use first available device" setting which will have the same effect as the "<default>" setting we had before. svn-id: r53771
Diffstat (limited to 'engines/sword1')
0 files changed, 0 insertions, 0 deletions