[Gzz] Re: [Fwd: Re: [Fwd: 2nd (Benja)]]

[Tuomas Lukka]

> >>- Allow views to have their own binders, passed to Fallback in the 
> >>constructor: there's a Map from views to FallbackBinders, and if a 
> >>window's current view is a key in that map, the corresponding binder 
> >>is used. Adding a new view and/or binder is done by modifying 
> >>Gzz.run() in Gzz.py.
> >
> >
> >Hmm. This assumes that the same view will always have the same binder -
> >is this too restrictive?
> >
> >OTOH, modes etc. should probably be done *inside* the binder.
> 
> Probably.
> 
> Besides, this is just a hack "for now."

Never make a hack "for now" that you wouldn't be happy with for
at least a year ;)

> >>PROBLEM: the view-specific binders are selected by the view of the 
> >>window that recieved the input focus, i.e., was front.
> >
> >
> >This should be indicated inside the window as well, somehow.
> 
> 1) We have far too many things to indicate in the window :-/ But I agree 
> this would be useful.
> 2) However, we need support from the GraphicsAPI for this, so that we 
> can know which window is front. I don't feel it's worth that, just right 
> now...

Umm, this is window-manager dependent: for me, I often want windows 
somewhat obscured to have focus. (focus follows mouse, not click-to-focus)

> Of course, I have window decorations that show me which window is front...
> 
> Also, I'd really like a fix for the problem here, which is that there 
> are multiple windows and only one view can determine the binder.

Well, I guess the focus would be the thing.

        Tuomas