CompuServe Thread

'status line indicators'… like the clock, huh? I'll try it. " A 16 color screen is going to flicker when you scroll it, there's no escaping it if you use RKM and Intuition friendly methods." Uhm… that turns out not to be the case. I'm using a _32_ color screen, and my program is quite RKM/Intuition Friendly. You want I should tell you how to double-buffer your display? Should be a lot easier than it was for me (2 screens, 6 windows, gadgets _and_ (&^$^%$) AnimObs)… no sarcasm, btw (well… maybe a _little_ <grin>). Jack, I do NOT want you to give up the CLI/Keyboard based 'interface' at all. I agree, once you get used to a program, in most cases, keyboard shortcuts are more efficiet than a GUI at text applications (like a term)… I would just like to see it 'GUIier' for the novice user. I think you do see my points, so I won't flog a dead horse anymore. I sympathise with your need for time. 24 hours/day is just not enough time to program and lead a life, too. If you care for any advice or help I can give (such as with the double-buffering), please let me know. –Eet– PS almost forgot, it only flickers with certain combinations of colors, obviously dependant on the bitplanes used. Assuming you're using the blitter for the scroll, blitting only the 1 or two planes involved in the scroll may eliminate the flicker. (unless there's some other colors on screen, in which case you can't :). Double-buffering should definitely be only an option, along with the deeper screens. That way, the user could avoid the memory/speed hit that double-buffering would give. Director of Mayhem Extra Terrestrial Imports, Ltd.