Thread View: comp.sys.next.misc
4 messages
4 total messages
Started by Paul Marcos
Sat, 19 Dec 1992 16:58
HOWTO: move windows w/o making key or ordering front
Author: Paul Marcos
Date: Sat, 19 Dec 1992 16:58
Date: Sat, 19 Dec 1992 16:58
90 lines
3496 bytes
3496 bytes
Enough people requested it to be a pain in the butt to
mail to everyone individually so here's how to do it:
There are 4 line changes and 2 line additions:
Lines 1176 through 1179:
change from:
5 index num //_frontWithClick exec
7 index 7 index 6 index
12 3 roll
4 index //buckyBitMask and
to:
5 index num
9 index 9 index 7 index
14 3 roll
6 index //buckyBitMask and
After Line 1181 (which reads 'icon 1 eq or {')
insert:
pop pop
After Line 1184 (which reads '}{')
insert:
//_frontWithClick exec
For those who care, the first 4 line changes basically
move the _frontWithClick call down to put it after the
Alternate key check. That call takes two arguments off
the stack (and leaves nothing) so the following index
parameters are all incremented by 2 so they just look over
the extra stuff that sitting at the top of the stack.
Then, if the Alternate key is down, it pops these two extra
items off the stack because it doesn't need them. If the
Alternate key is NOT down, then we call _frontWithClick
so that the window comes to front and is made key. At the
end of all of this, the stack looks no different than in the
old version so there shouldn't be any side effects of this.
Probably the easiest way to make the changes is to use Edit
or something and jump to the appropriate line numbers and
then do the changes.
Now logout, type 'exit' in the login window to restart
the windowServer and log back in.
Now the behavior of clicking in the title bar of any
window, menu or miniturized window will be as follows:
Click - Bring to front and make key
Click + drag - Bring to front, make key and drag
Click + Command - Send to back
Click + Alternate + drag - drag without changing
current window layer (Yeah!!!) and without
making key (Yeah!!!)
You know what I think is really stupid? Why didn't
NeXT just put this functionality in using the Shift
key or something? That way everybody could do whatever
they wanted and we'd all be happy.
Another quick comment. Somebody inquired why the app
icons don't snap to grids. The reason is because the
miniturized window icons are basically just a big square
title bar with no body. I haven't dug far enough to see
how the app icons are handled. Boy is this stuff just
screaming for a Preferences panel or what?!?!? Maybe
one of these days I'll completely rip apart the
windowPackage.ps file and make a Preferences panel that
lets you fine tune the windowServer to work the way you
want it to.
I'd like to thank the person who posted the snap icons
to grid message. They turned me onto the windowPackage.ps
file and that was a blast working through it. If you're
out there, drop me a line.
Enjoy.
Paul
P.S. Oh yeah, I take ***** NO ***** responsibility for
anything that may happen from making these changes. You're
on your own.
--
--------------------------------------------------------------------------
dCode | Internet: dcode@netcom.com | (415) 960-3539
NeXT Mail Happily Accepted
Re: HOWTO: move windows w/o making key or ordering front
Author: Volker Herminghaus-Shirai
Date: Sun, 20 Dec 1992 10:11
Date: Sun, 20 Dec 1992 10:11
53 lines
2025 bytes
2025 bytes
In article <1992Dec19.165840.8945@netcom.com> dcode@netcom.com (Paul Marcos) writes:
> Enough people requested it to be a pain in the butt to
> mail to everyone individually so here's how to do it:
>
> There are 4 line changes and 2 line additions:
>
> Lines 1176 through 1179:
> change from:
> 5 index num //_frontWithClick exec
> 7 index 7 index 6 index
> 12 3 roll
> 4 index //buckyBitMask and
>
> to:
> 5 index num
> 9 index 9 index 7 index
> 14 3 roll
> 6 index //buckyBitMask and
>
> After Line 1181 (which reads 'icon 1 eq or {')
> insert:
> pop pop
>
> After Line 1184 (which reads '}{')
> insert:
> //_frontWithClick exec
>
> For those who care, the first 4 line changes basically
> move the _frontWithClick call down to put it after the
> Alternate key check. That call takes two arguments off
> the stack (and leaves nothing) so the following index
> parameters are all incremented by 2 so they just look over
> the extra stuff that sitting at the top of the stack.
Are you sure? Seems to me you increment by two in all cases but one.
I.e. making the line
> 7 index 7 index 6 index
read
> 9 index 9 index 7 index
seems to me like incrementing 6 only by one instead of by two.
Please clear this up. I won't dare change my WindowServer before
I know what's going on here. (Then, however, I'll gladly do so :-)
Thanks anyway for the nice hack.
Volker
--
Volker Herminghaus-Shirai (vhs@qb.rhein-main.de)
Looks good on the outside, but -
intel inside
Re: HOWTO: move windows w/o making key or ordering front
Author: Alex Blakemore
Date: Sun, 20 Dec 1992 21:52
Date: Sun, 20 Dec 1992 21:52
26 lines
1450 bytes
1450 bytes
In article <1992Dec20.101130.1723@qb.rhein-main.de> vhs@rhein-main.de writes: > making the line > > 7 index 7 index 6 index > read > > 9 index 9 index 7 index > seems to me like incrementing 6 only by one instead of by two. I noticed the same thing and changed the 6 to 8 instead of 7 It seems to work, so I assume it was just a typo. I didnt try 7. It works great and also try alt-double click (to get the old behavior of alt-click) on a title bar. (bring to front but dont change key) alt-doubleclick and drag works too. so you get new features without losing any old ones. it sure makes reorganizing windows alot easier. > Please clear this up. I won't dare change my WindowServer before > I know what's going on here. I wouldnt worry too much, obviously save the previous windowserver package so if theres a problem you can boot single server and revert. -- --------------------------------------------------- Alex Blakemore alex@cs.umd.edu NeXT mail accepted
Re: HOWTO: move windows w/o making key or ordering front
Author: Paul Marcos
Date: Sun, 20 Dec 1992 22:57
Date: Sun, 20 Dec 1992 22:57
73 lines
2779 bytes
2779 bytes
In article <1992Dec20.101130.1723@qb.rhein-main.de>, vhs@rhein-main.de
(Volker Herminghaus-Shirai) wrote:
>
> In article <1992Dec19.165840.8945@netcom.com> dcode@netcom.com (Paul Marcos) writes:
> > Enough people requested it to be a pain in the butt to
> > mail to everyone individually so here's how to do it:
> >
> > There are 4 line changes and 2 line additions:
> >
> > Lines 1176 through 1179:
> > change from:
> > 5 index num //_frontWithClick exec
> > 7 index 7 index 6 index
> > 12 3 roll
> > 4 index //buckyBitMask and
> >
> > to:
> > 5 index num
> > 9 index 9 index 7 index
> > 14 3 roll
> > 6 index //buckyBitMask and
> >
> > After Line 1181 (which reads 'icon 1 eq or {')
> > insert:
> > pop pop
> >
> > After Line 1184 (which reads '}{')
> > insert:
> > //_frontWithClick exec
> >
> > For those who care, the first 4 line changes basically
> > move the _frontWithClick call down to put it after the
> > Alternate key check. That call takes two arguments off
> > the stack (and leaves nothing) so the following index
> > parameters are all incremented by 2 so they just look over
> > the extra stuff that sitting at the top of the stack.
>
> Are you sure? Seems to me you increment by two in all cases but one.
> I.e. making the line
> > 7 index 7 index 6 index
> read
> > 9 index 9 index 7 index
> seems to me like incrementing 6 only by one instead of by two.
>
> Please clear this up. I won't dare change my WindowServer before
> I know what's going on here. (Then, however, I'll gladly do so :-)
>
> Thanks anyway for the nice hack.
>
> Volker
>
> --
> Volker Herminghaus-Shirai (vhs@qb.rhein-main.de)
>
> Looks good on the outside, but -
> intel inside
Yes, that was a typo. I have tried it both ways and it seems to
make no difference. There is probably just something sitting on the
stack that ends up not being used. Interesting, though, why it
would work both ways.
I think the correct way to do it is to increment all parameters by 2
so the correct line would read
9 index 9 index 8 index
Good luck.
..............................
Paul Marcos
Kaleida Labs, Inc.
marcos@kaleida.com
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads