gzz-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Benja Fallenstein
Subject: [Gzz] Re: [Fwd: Re: [Fwd: 2nd (Benja)]]
Date: Thu, 03 Oct 2002 09:37:39 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1

-------- Original Message --------
Subject: Re: [Fwd: 2nd (Benja)]
Date: Thu, 3 Oct 2002 10:30:41 +0300
From: Tuomas Lukka <address@hidden>
To: Benja Fallenstein <address@hidden>
References: <address@hidden>

- 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."

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...

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.

- Benja






reply via email to

[Prev in Thread] Current Thread [Next in Thread]