Reply to Re: Midi Question
If you don't have an account, just leave the password field blank.
You're eating Pizza for lunch? Again? Jeez 
turn_midi_on() and turn_midi_off() are required if you assign midis to screens in the editor under certain circumstances. You can't control the playing of these assigned midis via script.
Let's say Dink is walking through a spooky forest, and there's a midi named 201.mid that sounds kind of spooky. So in Dinkedit or WinDinkedit, we'll set '201' as the midi number for all of the forest screens.
If Dink reaches the center of the forest, a giant evil toaster will awaken and start to chase Dink across screens. The spooky music that worked before doesn't work so well now... we want to play a high-action chase music midi (chase.mid). So we play that using playmidi("chase.mid");
But, dang, when Dink moves to another screen 201.mid starts to play. We don't want that.
So when we play chase.mid, we also issue the command turn_midi_off(), so 201.mid will not play unless we specifically tell it to. Once the toaster toasts Dink into another dimension, we'll issue the turn_midi_on() command so midis assigned to screens will play normally.
I hope that example explains things...
You could also use base scripts and playmidi commands to handle the playing of all midis (which is sort of what you were saying), but turn_midi_on() and turn_midi_off() would have no effect at all.
turn_midi_on() and turn_midi_off() are required if you assign midis to screens in the editor under certain circumstances. You can't control the playing of these assigned midis via script.
Let's say Dink is walking through a spooky forest, and there's a midi named 201.mid that sounds kind of spooky. So in Dinkedit or WinDinkedit, we'll set '201' as the midi number for all of the forest screens.
If Dink reaches the center of the forest, a giant evil toaster will awaken and start to chase Dink across screens. The spooky music that worked before doesn't work so well now... we want to play a high-action chase music midi (chase.mid). So we play that using playmidi("chase.mid");
But, dang, when Dink moves to another screen 201.mid starts to play. We don't want that.
So when we play chase.mid, we also issue the command turn_midi_off(), so 201.mid will not play unless we specifically tell it to. Once the toaster toasts Dink into another dimension, we'll issue the turn_midi_on() command so midis assigned to screens will play normally.
I hope that example explains things...
You could also use base scripts and playmidi commands to handle the playing of all midis (which is sort of what you were saying), but turn_midi_on() and turn_midi_off() would have no effect at all.
