<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Quoth John Harrison, on 18/02/10 15:24:
<blockquote
cite="mid:7aa995dd1002180724v79f40fd5y498af97f3de5b270@mail.gmail.com"
type="cite">Since you are on Linux one kludge might be to use <a
moz-do-not-send="true"
href="http://burtonini.com/blog/computers/devilspie">devilspie </a>to
force focus to a particular window?<br>
<br>
<div class="gmail_quote">On Thu, Feb 18, 2010 at 9:19 AM, James Dunn <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:james@4thharmonic.com">james@4thharmonic.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><font size="-1">Hi list,<br>
<br>
I have a patch where I'm running the audio in one instance of pd and
gem in another with -noaudio.<br>
I have the audio pd patch sending the output of [keyname] to gem pd via
[netsend], but after starting the patch in fullscreen the audio pd
patch loses the window focus. It works to begin with for a few
keystrokes, then I can no longer control the audio. I have a
[gemkeyname] object in the gem patch which then takes over (presumably
triggered by the gem activity that was controlled from the audio pd
patch), but I lose the audio pd control.<br>
I tried adding another netsend (on a different port) back to the audio
pd, but then I get some double triggers! <br>
<br>
So, what is the best way to maintain focus on one particular window? It
would be fine if the gem window has focus all the time, or the audio pd
window but I haven't worked out how and why it changes. I'm using
Ubuntu Hardy and pd-extended-0.42.5. <br>
<br>
thanks<br>
<br>
James</font><br>
</div>
</blockquote>
</div>
</blockquote>
<br>
Hmm, I think [linuxevent] might be the way to go. There's a post from
Hans in the archives that suggests adding the user to the input group
to open the keyboard, but I think the group is root? So is this really
the best way to input my keyboard as an ordinary user in pd? I'd rather
not have my everday user account with root priveleges.<br>
</body>
</html>