I've already looked into this with Marc's help, but I wanted it to make it
to the mailing list in case this comes back in the future, etc. I believe
that after working with Marc on this, the version of bbkeys in CVS (which
will be released as 0.8.4 whenever I get a spare day to look at it
again--go to http://sourceforge.net/cvs/?group_id=33459 in the meantime
for CVS access instructions) should now be functional with multi-head
displays, sort of. =:) The sort of comes in like this....
For those individuals who run multi-head displays, as it stands right now,
you'll need to run an instance of bbkeys for each display you want it to
work on, like this: "bbkeys -display :1; bbkeys -display :2", etc.
Now, from the pre-emptive "ssssssh" department (think Austin Powers),
before you start complaining about all the extra processing that bbkeys
will be taking up with a separate instance for each head, blah, blah,
blah, from what I understand of how The Other Window Managers (TM) do it,
it's the same end result. WindowMaker, I believe, fork()'s himself to
handle multi-head displays. And as a result, windowmaker's multi-head
handling is broken. So, before you start whining about having to run
multiple bbkeys versions if you have multiple displays, be forewarned that
I neither have the time or resources (I only have one display) right now
to try to correctly code multi-head logic into bbkeys by guessing at it.
I'll also say again that if anyone wants to contribute a patch of the
"correct" way to do this, I'm more than open to it.
So.
I guess that's all for now then.
Okay bye.
</vanRijn>
On 2001.10.22 18:59 Marc Wilson wrote:
> On Mon, Oct 22, 2001 at 02:42:53AM -0700, Tony Godshall wrote:
> > On Mon, Oct 22, 2001 at 12:50:01AM -0700, Marc Wilson wrote:
> > > Is there something I'm missing about bbkeys that would make it behave
> > > properly in a multiple-screen environment? Blackbox is more than
> willing
> > > to manage any and all screens it can find on the server, but
> bbkeys....
>
> <deleted>
>
> > > If only run on one screen, it can manage keys for that screen. Run
> another
> > > copy of it on another screen, and it stops working completely until
> you
> > > exit all copies of it running on all screens and start a single one
> up
> > > again.
>
> > I've had a similar problem, tho my multihead is in running
> > bbkeys in the native X terminal and also in Xvnc sessions
> > from other boxes. My temporary hack is to use another wm
> > inside vnc but I don't like it.
>
> Why would a copy of bbkeys running inside VNC care what the exterior
> window
> manager was doing? These things get weirder and weirder the more I look
> at
> them.
>
> I noted that blackbox, unlike most of the other wm's I've been playing
> with, doesn't actually fork another instance of itself to deal with the
> second screen... instead the one instance manages both. I imagine that
> if
> there were actually two X servers running, then there'd be two copies of
> blackbox running. Another great statement for minimalism, eh?
>
> At least that helps to understand why bbkeys has trouble with multiple
> running instances of itself. The instance that gets started on *:0.0 has
> no trouble at all hooking itself into blackbox, and then here comes
> another
> one on *:0.1 that messes things up. I suppose the actual fix will be to
> cause bbkeys to pay attention to keystrokes from any screen... not just
> the
> one it was launched on. It's not going to be a blackbox issue, I'd
> think.
>
> Anyway... I'd like to at least get my workspace switching back... the
> rest
> of the hotkeys I can live without. <wah!>
>
>
> >
> > --
> > T
> >
>
> --
> Marc Wilson
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
--
----%<----------%<----
Jason Kasper (vanRijn)
bash$ :(){ :|:&};:
Numbers 6:24-26
