On Sun, Jul 15, 2001 at 03:22:25PM -0500, xOr wrote:
> I've got another question, pertaining to my last email. As when a window
> is destroyed, the same thing occurs at startup, in the BScreen::BScreen
> function:
>
> if (! resource.sloppy_focus)
> XSetInputFocus(getBaseDisplay()->getXDisplay(), toolbar->getWindowID(),
> RevertToParent, CurrentTime);
> Should not something else be focused if sloppt is off. What would be
> really nice is if whetever is focused when sloppy is on, was also focused
> when sloppy is off (root window?) for both instances. This way keybindings
> would work correctly. Is it safe to just comment out both XSetInputFocus
> calls?
>
Well... is it safe? Yes... it's very unlikely that it will cause your
computer to explode. Wouldn't even crash blackbox.
Will click-to-focus work like it should? Maybe... but if it does, then
the keybindings won't work. The problem is that either some window gets
the focus, or no window does (and if you get rid of that line, I suspect
either could happen depending on the circumstances).
If some window got the focus, it would likely be the root window, and
you'll end up with a sort of sloppy-focus like effect (you'll be able
to type into windows even though they aren't explicitly marked the
focus window by blackbox).
If no window got the focus, then click-to-focus will work fine, but
no key events will be generated if no window was focused, and so the
keyboard shortcuts will stop working.
I should mention, though, that I haven't tested any of this... I'm just
going by memory of previous bugs & bug fixes related to input focus, so
it's possible that I'm completely off my rocker. Feel free to give it a
spin just to see what happens.
Jeff Raven
