Newsgroups: comp.sys.mac.system Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner From: dorner@pequod.cso.uiuc.edu (Steve Dorner) Subject: Re: ScrollBar design question Message-ID: <1991Jun27.184247.6241@ux1.cso.uiuc.edu> Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at U-C References: <22430@duke.cs.duke.edu> <54350@apple.Apple.COM> Date: Thu, 27 Jun 1991 18:42:47 GMT Lines: 30 In article <54350@apple.Apple.COM> keith@Apple.COM (Keith Rollin) writes: >There are three reasons that I can see that "live scrolling" wasn't >done. >for space and not for speed, and an 8MHz 68000. There just wasn't >enough horsepower to do that kind of scrolling. Amen. >there is no way for the >scrollbar to automatically scroll the window. > >again without something like MacApp, there is no way for the >scrollbar to know which areas to scroll. You and I must not be using the same scrollbars. The scrollbars I use have a hard time doing anything at all without me holding their little arrows, much less knowing how to scroll part or all of my window. I don't see how live scrolling is conceptually harder than handling presses on one of the scroll-bar arrows; you'd handle it in pretty much the same way, with a callback to the application, *IF* the hardware were fast enough. I submit that the hardware is still NOT fast enough, except *perhaps* on a ci or fx in 1 bit mode, for most applications. I'm quite happy with live scrolling on my 25MHz 68040 box, but I just can't see it on a 16MHz 68030, much less these 8MHz 68000's Apple is still selling truckloads of. -- Steve Dorner, U of Illinois Computing Services Office Internet: s-dorner@uiuc.edu UUCP: uunet!uiucuxc!uiuc.edu!s-dorner