<br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Spencer Salazar</b> <<a href="mailto:ssalazar@cs.princeton.edu">ssalazar@cs.princeton.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ideally, the console monitor in miniAudicle could send<br>keystrokes to KBHit, but this hasn't been implemented yet.</blockquote><div><br><br>The main strength of this would be that in this case one could make sure that actions like typing a email or editing a softsynth while the the Mini is listening for events don't accidentally affect the Mini (I myself tend to find this amusing and to result in "happy accidents" but I could imagine it being unwanted).
<br><br>So, if we know this and know the HID approach is more powerful another take on this matter might be something like this;<br><br>Machine.hasFocus(int) //returns 1 is the mini/Audicle/console window has the OS focus, 0 otherwise
<br><br>This would allow programmers to use the more powerful implementation while having the option to use the KBHit style behaviour, even on a per-device basis. Sadly this feature would require a different implementation for our three platforms which could be a drawback but aside from that it seems win/win.
<br></div><br>Luigi; I would have loved to help you but feel unqualified to talk about such details of OSX behaviour because iI don't have a OSX install. KBHit seems to me like a prime canidate for system dependant behaviour.
<br><br><br>Yours,<br>Kas.<br></div>