<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">it would be interesting to know what system you are on<br></blockquote><br>Formerly I was using OSX
10.4, but since a couple of weeks I've been working on Windows XP. On OSX I used [gemkeyname] exclusively to trigger movement. So I don't know if this problem of lowercase/uppercase was there on OSX as well. I suppose it wasn't, since it shouldn't be a problem at all.
<br><br>I ran Ubuntu Studio on this pc through VirtualBox but there I had a problem with the channeling of the USB ports. So the Arduino I'm planning to implement in the installation can't be seen by pure data in Ubuntu Studio. Since this computer i'm working on isn't mine, partitioning and risking problems with that is not really an option. Once a week I do some testing on both platforms OSX as wel as WindowsXP. I'll try to test the uppercase/lowercase problem on OSX tomorrow. Eventually the installation will be running from OSX, so I hope that in the end [gemkeyname] can be used without a problem.
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">in this case [keyname]/[key] won't help you, since they only work when<br>they have the keyboard focus (which they don't when the gemwindow is
<br>before them)</blockquote><div><br>I'll be projecting the gemwindow on a surface, so maybe there's a way to use a split screen (on OSX) and to have the keyboard focus? Since the computer screen will not be visible for the user.
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">a good way to get the keyboard regardless of the the window-focus is<br>[hid] (and probably [hidin])
<br></blockquote></div><br>Seems to be a problem on WindowsXP? I could try this on OSX, because that's where the patch should be running smoothly in the end. Would this (hid/hidin) be the best option?<br><br>And o yeah: The version of pd is pd039ext, so I thought maybe this could be the problem. I needed the update to get the Arduino to work properly. I've read recently about problems with Gem in combination with pd039ext. Could this be the main cause? If this is so ... it's a shame :)
<br><br>And at last (for now): I found the "kiosk" patch. Looks very interesting, thanks a lot. But I don't know what to do with the kiosk.diff file. I'm sorry if this is a newbie question. It would be great to be able to use this function.
<br><br>Thanks all,<br><br>yorick<br><br><br><br><div><span class="gmail_quote">2007/6/12, Steffen <<a href="mailto:stffn@dibidut.dk">stffn@dibidut.dk</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On 12/06/2007, at 8.45, IOhannes m zmoelnig wrote:<br><br>> Yorick Phlypo wrote:<br>><br>>> Except for the keycombinations like ctrl+Q again. At this point I<br>>> have<br>>> no idea how to work around this.
<br><br>[snip]<br><br>> oh, and don't forget to remove the Control, Alt, Meta keys from your<br>> keybaord, as people will likely keep rebooting your machine....<br><br>Isn't it possible, like generally, to instruct the operating system
<br>to ignore (or similar) unwanted keys (or key combinations)?<br><br>As i understand what Hans says, then HID and friends basically just<br>listens to the operating system. This motivates the above suggestion.<br></blockquote>
</div><br>