Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!aplcomm!capd.jhuapl.edu!waltrip From: waltrip@capd.jhuapl.edu Newsgroups: comp.sys.next Subject: Re: Comments about the NeXT interface Message-ID: <1991Jan28.110558.1@capd.jhuapl.edu> Date: 28 Jan 91 16:05:58 GMT References: <1991Jan26.200500.22284@magnus.ircc.ohio-state.edu> Sender: news@aplcomm.JHUAPL.EDU Distribution: na Organization: CAPVAX, JHU/APL Lines: 38 In article <1991Jan26.200500.22284@magnus.ircc.ohio-state.edu>, mitroo@magnus.ircc.ohio-state.edu (Varun Mitroo) writes: > [...some material deleted...] > > I don't really mind click to focus, but what really bothers me is that > clicking > anywhere in a window brings it to the front, hiding any overlapping windows. > Why can't clicking in a window activate it, and maybe clicking on the drag > bar or double-clicking would bring it to the front. The NeXT has a nice, > large > screen, but I feel like I have to constantly rearrange windows to avoid any > overlap. > Lot of good points in this post which nicely avoided the religions aspects of this issue. The GUI I'm used to is DECwindows which is a click-to-focus environment so naturally I'm comfortable with it. But this point about bringing-to-front being tied in with focus does cause problems. In DECwindows, there's a put-behind box associated with the window dressing. Seems like this is an area where "good ideas" might be welcome as suggestions. [...more material deleted...] > > One idea is to make move to focus work as soon as a mouse button or key > is pressed in a different window. Also, windows should NOT come to the front > just because they are active - there should be a gadget to press to make it do > that. > Seems reasonable to me. [...more material deleted...] c.f.waltrip Internet: Opinions expressed are my own.