The Keyboard.KeyDown event fires double as expected. So does the KeyUp event, but that just might be a side effect. On closer inspection, the event only gets fired once, but the Debug.WriteLine call within it fires twice as I step through it. I have never seen a single step over a Debug.WriteLine cause it to run twice. Odd, but likely my issue not AgateLib. ^_^ |
|||
|
|
Yeah, the doubling of
Yeah, the doubling of Debug.Write* output is due to the code in Core.Initialize. It installs a trace listener to direct debug output to the console. It's there because (at least when I put it in a while back) Mono didn't direct debug output to the console, so adding this allows for debug information to be collected when running on Mono. Of course, Visual Studio also does the same basic thing, so on Windows you get the output twice. I never bothered to write and test the conditions to make this happen only when it needs to.