ben@ut-emx.UUCP (Benjamin J. Sloan) (02/05/90)
If memory serves me correctly, in former versions of the Mac system software, holding down the option key while double-clicking to open folders had a special meaning. It meant that the open windows were not remembered by the Finder so that they were not left open the next time your returned to (reloaded) the Finder. This was very handy for times when one had to dig deep into many folders when opening something and didn't want all those folders open upon returning to the Finder. As of at least system 6.0.4, holding down the option key while opening folder windows causes previous windows to close leaving open only the last window opened. When returning to the Finder from an application, the last window opened is still on the screen. What gives? Ben Sloan UT Geology ben@pluton.geo.utexas.edu
doron@cfdl.larc.nasa.gov (Doron Kishoni) (02/08/90)
In article <24087@ut-emx.UUCP> ben@ut-emx.UUCP (Benjamin J. Sloan) writes: >If memory serves me correctly, in former versions of the Mac system software, >holding down the option key while double-clicking to open folders had a special >meaning. It meant that the open windows were not remembered by the Finder so >that they were not left open the next time your returned to (reloaded) the >Finder. This was very handy for times when one had to dig deep into many >folders when opening something and didn't want all those folders open upon >returning to the Finder. > >As of at least system 6.0.4, holding down the option key while opening folder >windows causes previous windows to close leaving open only the last window >opened. When returning to the Finder from an application, the last window >opened is still on the screen. > >What gives? > >Ben Sloan >UT Geology >ben@pluton.geo.utexas.edu Well, whatever the reason is, I like it! Together with a modified flag in the LAYO resource of the Finder, namely: the "Title Click", I can now dig into a deep folder without leaving all of them open, as you said. To get back to the parent folder, I just double click on the title of the window. Now, if I could just be able to close the original (deeper) folder when its parent opens....
folta@tove.umd.edu (Wayne Folta) (02/09/90)
>> [reference to Option-clicking a folder in 6.0.4] > [reference to "Title Click" enablement] >Now, if I could just be able to close the original (deeper) folder when >its parent opens.... Strangely enough, if you hold down the option while clicking on the title bar, you open the parent, and close *its* parent if it is open. At least that is how I remember it. This sounds consistent from the coding standpoint, but it would be more consistent from a user standpoint if it worked as you have suggested. -- Wayne Folta (folta@cs.umd.edu 128.8.128.8)
jackiw@cs.swarthmore.edu (Nick Jackiw) (02/09/90)
ben@ut-emx.UUCP (Benjamin J. Sloan) writes: > As of at least system 6.0.4, holding down the option key while opening folder > windows causes previous windows to close leaving open only the last window > opened. When returning to the Finder from an application, the last window > opened is still on the screen. > > What gives? > > Ben Sloan This presumably relates to the fact that an increasing number of users now run Multifinder. In Multifinder, Finder never quits, so the old option-key meaning (close windows on quitting Finder) never has a chance to operate (except, I guess, after a Shutdown or Restart). The new behavior, called "tunneling," is meant to assist you in limiting open windows in the Finder without ever having to quit the Finder. -Nick -- -----Nicholas Jackiw [jackiw@cs.swarthmore.edu|jackiw@swarthmr.bitnet]----- "Here is how I built this artificial mine. I snatched a female louse from the hair of humanity. I was seen to lie with her on three successive nights, and then I flung her into the pit." _Maldoror_, Canto II
ts@cup.portal.com (Tim W Smith) (02/10/90)
< Well, whatever the reason is, I like it! Together with a modified flag in
< the LAYO resource of the Finder, namely: the "Title Click", I can now dig
< into a deep folder without leaving all of them open, as you said. To get back
< to the parent folder, I just double click on the title of the window.
<
< Now, if I could just be able to close the original (deeper) folder when
< its parent opens....
Here's an FKEY to do this, followed by instructions::
-----------------------------------------------------------
(This file must be converted with BinHex 4.0)
:"e9`)%C,49N!2j!)!*!)!QB8m!#3"!%!N!-#,!!!!5`!N!-kCA"XB@0P)'9iDA0
dD@jR)0*H-0-J2`#3"%S!!3#3!`G9F#"'5d9C!J#3!cq3#!%!!)!"!*!&22)!!$q
3#!%!!)!"!*!%K!#3$U(j0@i!N!B#CJ!!-J"`!%3!ZJ3#6dX!N!81!"!!,J#kL#p
#B@3JBfKKFQ&MG'9b)'PZ)'jKE@8X)'pb)'0KEY9d)'CTEQ3JG'KKG#"NDA0V,J#
3"&S!!3#3"8)!F!"5!,S%!Np,!*!&$J!3!$i!ZSJk@@pe)'4[)'j[G#"SBACP)(4
SC3!!!5KJ#J!!4NY&@3!'!!"*q[rb5(S!"Nje6R919[r`5RJ"K'C'3UHT*#"I,8M
rm%UZrr"R!!$J)'lrm%US!*!!Ca`JE[r`)'J!N!"++!"ZC`iJE[r`,bJ!N!#T(f!
!!,Sr2!!B3QG1ZJ#mB!!!V%+RU53JAbe)rrK)E[rdU(3[,[riU(-JE[ri,@J!%2r
m5'lrr+K`,blrp+Kc,cJ)-#!ZrraB3%K!@8")3#(!#$!r1!&k2cJ"K$(m!!!"HM(
m!!!"K$"m!!'J,c"m!!+J,c"m!!'J,c"m!!+J,c(I!B3ah`&k)Gm)-$"m!!-`1!'
%S#m`I!!%-$J"K+![-(`!!h!!-$`09k![-(`!"(!!-$`09k![5RJ"K'Ek6Pj1G8e
"58iJN!3LAb!I,`QJ-Nje!!!"!*!$!L`!!!%X!*!$1J!e@Q!'RJ#3!a`!-J!!4NY
&@3#3!`S!"J!!)!#3"`G0EhCP)&9`'J3:
------------------------------------------------------------
Install it in Finder. Enable "Title Click" in the LAYO resource.
When you invoke this FKEY, it will double-click on the title bar
of the frontmost Finder window, and then close that window after
the new window appears.
Some warnings:
1. This closes windows by doing a pretzel-W. If your
Finder has had it's command key assignments changed,
this will fail.
2. This FKEY plays with some low memory globals, so
don't be surprised if it breaks in the future.
3. The window that gets closed is the window that ends up
second after the title click. Thus, if you do this from
the root, you will not go anywhere, and if there are any
other Finder windows opened, one of them will get closed.
4. This was a quick hack one evening. It seems to work,
and I've had no problems in the many months I've used it.
5. If you have some sort of FKEY manager that, say, gives
you a list or pop-up menu of FKEYS and lets you chose one,
you probably can't use this FKEY with it. See the source
code below if you want to know why.
I've also got an FKEY that goes down, if anyone is interested. This
is not that useful, now that 6.0.4 has the option-open feature, but
I can post it if anyone wants.
Following is the source code, in Think C, for those who are curious,
or who want expand upon this. It's not clear that this is the right
way to do this sort of thing, by the way. As I said, this was a
quick hack. Oh, tabstops should be every 4 if you want this to look
pretty.
--------------------------------------------------------------
/*
* Here's the plan:
* 1. post a double-click in the title bar of the frontmost window
* 2. wait for the parent window to appear
* 3. select the second window
* 4. post a COMMAND-W
*
* The problem here is between step 2 and 3. If we leave the FKEY to let
* the Finder bring forth the parent window after step 2, we aren't around
* to perform step 3. Note that we can't get the Finder to do step 3 by
* posting a mouse down event in the second window because the second
* window may be completely covered by the first window.
*
* This leads to the modified plan:
*
* 1. post a double-click in the title bar of the frontmost window
* 2. post a COMMAND-SHIFT-NUMBER keyboard event, where NUMBER is
* the number of this FKEY
* 3. Return to Finder
* 4. Finder makes parent window appear
* 5. COMMAND-SHIFT-NUMBER is processed, bringing us back to the FKEY
* 6. select the second window
* 7. post a COMMAND-W
*
* Now we have a different problem. The FKEY is invoked twice. Since it has
* no global variables that will stick around between the two invocations, how
* to we tell them apart? We will let the user do it for us! The first time
* around, we will wait for the user to release one of the COMMAND, SHIFT, or
* NUMBER keys before returning to the Finder. This lets us tell which pass we
* are on: if the keys are down, it is the first pass; if they are up, it is
* the second pass.
*
* This leads to the final plan of attack:
*
* 1. Check the keyboard status to see which pass we are on
* 2. if first pass, then
* 2a. post a double-click in title bar of front window
* 2b. post keyboard events to reinvoke FKEY
* 2c. post COMMAND-W
* 2d. wait for user to release key
* 2e. return to Finder
* 3. else
* 3a. select second window
* 3b. return to Finder
*/
void main( void );
void begin( void );
/*
* When we are invoked for the first time, STILL_DOWN will be true.
* When the user releases one of the keys, STILL_DOWN will become false.
*/
#define STILL_DOWN (*(unsigned short *)0x184 != 0)
/*
* Begin is here to get the proper FKEY header. Make sure you have
* the custom header option checked in Think C!
*/
void begin()
{
asm
{
bra.s @1
dc.w 0
dc.b 'F','K','E','Y'
@OurID:
dc.w 6
dc.w 0
@1: lea begin, A4
pea main ; I have no idea why I didn't use jmp...
rts
}
}
void main()
{
long p;
long * pp;
GrafPtr savePort;
if ( ! STILL_DOWN )
{
/*
* Second pass. We need to get the window zapped.
*/
WindowPeek front;
front = (WindowPeek)FrontWindow();
if ( front == 0 )
return;
/*
* If the second window is "reasonable", we will select it and let
* the COMMAND-W zap it. If it is not reasonable, then the user
* probably did something like try to move up from the root.
* In this case, we get rid of the COMMAND-W.
*/
if ( front->nextWindow != 0 && front->nextWindow->visible )
SelectWindow( front->nextWindow );
else
FlushEvents( keyDownMask|keyUpMask, 0 );
return;
}
/*
* First pass. First step is to find the title bar of the front window
*/
pp = (long *)FrontWindow();
GetPort( &savePort );
SetPort( pp ); /* so LocalToGlobal will work like we want */
p = pp[4]; /* top left of window... */
LocalToGlobal( &p ); /* ...in global co-ords */
SetPort( savePort );
asm
{
;
; make PostEvent think that the mouse is in the title bar
;
move.l 0x830,-(a7) ; this is where _PostEvent gets the mouse
; ...location from. We are going to
; ..."borrow" it.
move.l p, d0 ; Co-ords of top left of window
add.w #4, d0 ; We compute the co-ords of
swap d0 ; ...a point 4 pixels over
sub.w #4, d0 ; ...and 4 pixels up. This
swap d0 ; ...is where we will put our
move.l d0, 0x830 ; ...imaginary mouse
;
; Now we can post the double-click!
;
move.w 0x17a,-(a7) ; These are where _PostEvent gets the state
move.w 0x184,-(a7) ; ...of the keyboard.
move.w #0,0x17a ; We want _PostEvent to think that no keys
move.w #0,0x184 ; ...are pressed.
move #1, a0
_PostEvent ; mouse down
move #2, a0
_PostEvent ; mouse up
move #1, a0
_PostEvent ; mouse down
move #2, a0
_PostEvent ; mouse up
move.w (a7)+,0x184 ; we can stop lying to _PostEvent now
move.w (a7)+,0x17a
move.l (a7)+,0x830
;
; The shift and command keys should still be down from the original
; invocation of this FKEY
;
move.w #3, a0 ; key down
move.w 0x184, d0
_PostEvent
move.w #4, a0 ; key up
move.w 0x184, d0
_PostEvent
move.w #3, a0 ; key down
move.l #0, d0
move.w #0x0d00|'W', d0
_PostEvent
move.w #4, a0 ; key up
move.l #0, d0
move.w #0x0d00|'W', d0
_PostEvent
}
while ( STILL_DOWN )
;
}doron@cfdl.larc.nasa.gov (Doron Kishoni) (02/13/90)
>> [reference to Option-clicking a folder in 6.0.4] >> [reference to "Title Click" enablement] >>Now, if I could just be able to close the original (deeper) folder when >>its parent opens.... > >Strangely enough, if you hold down the option while clicking on the title >bar, you open the parent, and close *its* parent if it is open. ...... >-- hmmm! This is really interesting.. To add to the confusion, it looks like only the root directory will close, and only is some other immediate parent opens (ie, was previously closed). Well, system 7.0000 might solve all the misteries (??)
dkelly@npiatl.UUCP (Dwight Kelly) (02/13/90)
doron@cfdl.larc.nasa.gov (Doron Kishoni) writes: >>Strangely enough, if you hold down the option while clicking on the title >>bar, you open the parent, and close *its* parent if it is open. ...... If you hold the option key down and open a folder, Finder closes its immediate parent. If you hold the option down and click on the close box, the Finder will close the window and ALL of its parent's windows! Neat! Cool! Dwight Kelly Network Publications, Inc. Atlanta, GA