I think I found out that the platform would emit the mouse movement events at up to 60fps, so I just tweaked the timer to match that. (This timer would be canceled if the mouse was moved out of the auto-scroll region.) If you continually moved the mouse, then it's possible the application would get the mouse movement events at a higher rate than the timer would fire, so the scrollable area would scroll faster. My code listened to mouse movement events, and if a selection was present and the mouse was moved into the top or bottom regions of the scrollable area, then the area would scroll a bit, and a recurring timer for some number of milliseconds would be started (if already active, then it would be reset) which would case the area to scroll a bit more. I've implemented the behavior of 'scroll the field down while the user is holding something selected' before, and my initial implementation had this bug, so I think I can explain a likely reason this happens. not, because the kernel will consistently see that the task is not keeping the CPU it's scheduled on loaded above a threshold, so the clocks will go down all the way to idle. Then you would see the measured duration decrease when your finger was on the screen vs. This is all the same as 'regular' linux as it's just an aspect of most governors (ondemand, interactive, etc.)Īs in, touching the display will never make this loop go faster: If you have a process that has short bursts of work, though, then the duration of that burst will definitely vary in response to touch boost. If you have an actually loaded background process on Android it by itself will keep the clocks high. Only if they do not have enough load, that is. > A somewhat similar effect is alive and well on Android: background processes run measurably faster while user holds/moves their finger across the screen

I still have that one, found it while moving ) Then I sent it in with what was probably all of my hard earned beer money for upgrade to a Courier v.Everything. somehow just before college I got a used USR Courier HST. My Dad was purple he was so angry and I worked a lot of odd jobs to pay that off. I had a good old time until the bill came. It was great! Active! Doors! gFiles! Warez! But was actually zones away in Texas. And then I made a mistake and on the advice of another BBS'er tried one in what I thought was a neighboring LATA. I tried to stay within my LATA which included Sherwood Forest, Camelot, some others with doors and FIDO that can't recall. I got myself a Hayes 2400 and convinced my dad to get the fixed calling within your area code which I mostly paid for with my part-time work. First with a Practical Peripherals modem that my dad acquired to dial into his business (which still used teletype). staying up late at night or waking up early before school to login to BBS's.

Windows 98 cursor animated