Re: [e-users] enlightenment 0.16.8.5 ignores switch focus to previous window

[Kim W. <ki...@wo...>]

Warren Crossing wrote:
> my grokking revealed a few of e16s inner secrets
> 
> clicking on warp focus win does switch focus but doesn't hilight item in 
> warp focus window
> 
Should now be fixed in CVS.

> sometimes focuslist doesn't go away
> 
This has been a coming and going problem in ages. I don't see it atm. so 
I have been assuming it was gone. Please provide steps to reproduce.

> and primarily
> 
> traversing the warp focus list reorders the stacking lists so traversal 
> order is unpredictable ( only when focus settings -> raise window after 
> focus witch)
> 
There also is the focus stack which also is reordered if you select 
focus while switching. The focus stack is the one determining the focus 
list item order. It is sampled when the focus list is activated and this 
sampled list is not reordered while the focus list is mapped, so I don't 
think the traversal order is unpredictable.

> mapped keys will show the warp focus window but are not detected once 
> warp focus window is shown i.e it uses XKeys TAB codes directly how it 
> works is tab is handled specially, when you A/T the first time it shows 
> the warp focus window, releasing TAB then you can press up or down, 
> pressing TAB again warps forward.
> 
Yeah, I see there is some uglyness around the Tab key. I'll try to sort 
that out one of these days.

> my coding is pretty slow and shakey and there are a bunch of worms, to 
> do with es' WHY flags and the Xkey event system.  I'll take it on as 
> more of a hobby at this stage =)
> 
> but the short answer as to why alt/some key wont map to previous is 
> because it can't remember what actually happened.. (and another bug is 
> masking the behaviour) so best to work around it using ALT/UP and 
> ALT/DOWN me thinks.
> 
Not sure that is correct. As the focus stack is sampled when the focus 
list is shown it would be simple to restore it when the focus list is 
unmapped. It would also be possible to sample/restore the layer stack.
However, I doubt that really is what you want. I suspect that the 
problem you are seeing is caused by the questionable(!) mapping of the 
invoking key code to XK_Tab.

/Kim