Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!polyslo!dorourke From: dorourke@polyslo.CalPoly.EDU (David M. O'Rourke) Newsgroups: comp.sys.mac Subject: Re: finder irritations Message-ID: <1989Oct17.220051.25171@polyslo.CalPoly.EDU> Date: 17 Oct 89 22:00:51 GMT References: <111900082@uxa.cso.uiuc.edu> <1166@key.COM> Reply-To: dorourke@polyslo.CalPoly.EDU (David M. O'Rourke) Organization: Cal Poly State University -- San Luis Obispo Lines: 26 alms@cambridge.apple.com (Andrew L. M. Shalit) writes: >Sounds like a good use of the ol' command key in the next version of >the finder. As you know (maybe) holding down the command key when you >click in the title-bar lets you move a window without selecting it. >Shouldn't be too hard to extend this to work for selecting files. >Of course, it would have to be done by the people who write the >finder. I remember hearing somewhere that the 'new' finder will not bring a window forward, or some such, until a mouse-up. So you press the button on the file, and if you keep the button down {very reasonable assumption IMHO} then you're proably doing a file-drag for a copy or some such. Having played with this idea some in my current projects it works quite well. The users really don't care if a window isn't selected until the mouse-up, and in fact I personal haven't noticed much difference in operation as far as window selection goes. This is all based on memory, and I might be confused... But if I am confused I'd like to submit this idea as a possible solution. Seems elegant {sp??} to me, so that must mean I didn't think of it. :-) -- \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\|///////////////////////////////////////// David M. O'Rourke____________________|_____________dorourke@polyslo.calpoly.edu | Graduating in March of 1990, with a BS in Computer Science & need a Job. | |_____________________________________________________________________________|