|
From: Anthony K. <ant...@sb...> - 2007-01-05 20:25:26
|
Bernard Bel wrote on 1/4/07 4:45 PM: >> OK ... yesterday I was trying to get some actual development done amidst all >> of the release preparations and I was attempting to disable the built-in >> MIDI driver at compile-time. > > Is this happening with the 2.9.5 version, or with the version in which this > in-built MIDI driver code has been disabled? This is happening with my "in development" version where I have forced DriverOpen() to return an error code. Clearly, more than just returning an error will need to be done. >> I found that if I turn off OMS with the built-in driver omitted that BP2 >> hangs. > > Does this also happen if you start the program with "-se.startup" in which > "Use MIDI in/out" would be off? It does not happen if I turn off MIDI in/out before turning off OMS. However, if I then save -se.startup with both of these off (and the built-in driver disabled by the compiler), BP2 will just exit from main() after trying to load both Midi drivers. I discovered that it is not actually hanging, it just seems to ignore all events for an extended period. Eventually, I can switch back to CodeWarrior but the "pause" happens again when switching back to BP2 and I can never actually do anything in BP2 (except switch out). > I need to check in the code. For the time being, leave the in-built driver as > it is, if you can backtrack to that version, and I will send you asap athe > list of all that is implied at startup. No need to rush or spend a lot of time coming up with a solution right now. I looked at it some more this morning and I think that I will just leave the issue for the moment. The Carbon version will eventually have to leave both OMS and the built-in driver behind, but I can continue with many other things before solving this issue. Thanks. Anthony |
