🚀 go-pugleaf

I said, with respect to depth gadgets:
> >Try using 'click' as a toggle: if it's obscured, bring it to front. Otherwise
> >drop it to back.

In article <3400@crdgw1.crd.ge.com> barnett@crdgw1.crd.ge.com (Bruce Barnett) writes:
> Example: I want to look at a large window 'cause it has a manual page,
> data or source, but do work in a smaller window on top of the first.

> Then I want to select something in the "back" window and
> move/copy/paste it in front. BANG! my small window goes away. Grr!

I agree. That's a total botch. That's why I didn't suggest it.

I was talking about how to overload to-front/to-back on a single gadget,
so you don't have to have two depth-arranging thingies.

> >What does 'selecting' a border usually do?

> Bingo!

> A lot of window systems use clicks on the border of a window to
> specify window-manager actions.

And of course the border is just a *fine* depth/resize gadget. Go back and
re-read the article I was following up to.

> But inside the window, you can make that program use any sort of
> chord like
> 	 Shift-Meta-Control-DoubleClick left, middle and right mouse buttons.

Noooooo!

chording/double-clicks/etc are a kludge. One button -> one action. If you
want to do something more complex, use a menu or a poke point.
-- 
Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation.
Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-'
"I feared that the committee would decide to go with their previous        'U`
 decision unless I credibly pulled a full tantrum." -- dmr@alice.UUCP