Hello Michael,
I am not using Java apps much, so I did not realize this behaviour
until your mail, but I have the same problem.
I found that "client.focus" is not set after
"awful.client.focus.byidx" if target is a Java app. Someone who knows
awesome internals may explain what is going on and provide a better
solution.
In the meantime following hack works for me. In rc.lua:
awful.client.focus.byidx = function (i, c)
local target = awful.client.next(i, c)
if target then
client.focus = target
end
return target -- I added this -- since client.focus not set,
get target client
end
Then instead of:
awful.client.focus.byidx( 1)
if client.focus then client.focus:raise() end
using:
target = awful.client.focus.byidx( 1)
if target then target:raise() end
Downside: All clients whether focusable or not will be raised.
On 20 March 2012 16:03, Michael McDermott <[email protected]> wrote:
> Hello,
>
> When I use Awesome WM (which lives up to its name, by the way) and I
> run FreePlane or FreeMind, I run into an interesting issue: if I
> switch focus to the window using Mod4+j or Mod4+k, the item highlights
> as though it has received focus, but the window is not brought into
> view. So, for example, if I view tag #1 which contains a Firefox and a
> FreePlane window (both maximized) and then I press Mod4+k to switch to
> FreePlane, the item in the "taskbar" highlights, but Firefox continues
> to fill the screen.
>
> I suspect that the issue is Java-related, as the same thing happens
> with other apps (I downloaded TripleA to verify this).
>
> At present, the only Java hack I am running is that wmname LG3D is in
> my .profile.
>
> Is there anything I can do to resolve this focus weirdness?
>
> Thanks,
>
> Michael
>
> --
> To unsubscribe, send mail to [email protected].
--
Can Altıparmak
--
To unsubscribe, send mail to [email protected].
