Xref: utzoo comp.sys.amiga:20520 comp.sys.amiga.tech:1131 Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!cbmvax!joe From: joe@cbmvax.UUCP (Joe O'Hara) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: Active Window (Re: An annoying feature of 1.1,1.2, etc that I want gone) Keywords: Suggestion Message-ID: <4120@cbmvax.UUCP> Date: 27 Jun 88 13:26:59 GMT References: <4023@pasteur.Berkeley.Edu> <135@quintus.UUCP> <2166@sugar.UUCP> <339@boing.UUCP> <137@quintus.UUCP> <341@boing.UUCP> Reply-To: joe@cbmvax.UUCP (Joe O'Hara) Organization: Commodore Technology, West Chester, PA Lines: 27 In article <341@boing.UUCP> dale@boing.UUCP (Dale Luck) writes: >In article <137@quintus.UUCP> pds@quintus.UUCP (Peter Schachte) writes: >> >>The pointer should be set not only when the window is first opened, but also >>every time it is given focus by being clicked in. >>I don't think you want a REAL stack, as it would grow pretty fast if you >>click around much. > >Right, the implementation does not necesarily need to follow the >semantics of the feature. All it needs to do is look like a stack. >When ever a window becomes active, a time stamp could be placed in the >window structure. When the window is deleted intuition just looks for >the most recently activated window. Simple enough? > This method also gets around, stale backward activation pointers. >And what do you do when the window you are now going to activate because >the present one is being deleted does not exist. Another approach would be two pointers in the window structure, PREV_Window and NEXT_Window. When a window in the middle of the chain closes, it's a simple matter to update the pointers in the affected windows. -- ======================================================================== Joe O'Hara || Comments represent my own opinions, Commodore Electronics Ltd || not my employers. Any similarity to Software QA || to any other opinions, living or dead, || is purely coincidental. ========================================================================