On Wed, 15 Nov 2000 23:01:14 Jeff Raven wrote:
> Yeah, you'd need to change bbkeys too. The thing with Windows-style
> cycling is that if you want to keep cycling you don't release the
> ALT key. Blackbox doesn't pay any attention to this, since it just
> looks for window cycling messages from bbkeys.
>
> The other problem is that the most natural way to keep track of
> windows for Windows-style cycling is via the stacking order (if
> I recall, it essentially just swaps the two top-most windows
> unless you keep the ALT down), and at present Blackbox doesn't
> make this information available to outside programs.
>
> Now, since the stacking order is part of the NET WM spec, Blackbox
> will provide it in the next major release, but that will be a little
> while -- I'm more or less going through the code line by line, rewriting
> things as I go (and then rewriting them again, and again... I'm too
> damn picky sometimes).
Hmm, guess I will go ahead and finish my patch since it might be a while.
:) It is pretty easy, but probably not the best way. Since BB already has
nice linked list functions, I just created another linked list in
Workspace.cc called positionList, and whenever a window is
added/removed/raised, the window number is inserted/removed/shifted.
Then in Screen.cc, I have the nextFocus function simply read the first
unshaded window. Problem is they just cycle between eachother. Is there a
way, that for instance, bbkeys could send a parameter along with the next
focus message? Have the parameter be a count of how many times it has been
pressed, then just have next focus load that position's window.
BTW: Just started using BB, love it. Nothing like a fast wm for speed
freaks.
Ken
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Ken Robertson [EMAIL PROTECTED]
qgyen.net sysadmin www.qgyen.net
