You're reading a message in a looooong thread in threaded view. You're ready to read the next message. You look below, and see zillions of replies. You scroll and scroll till you find the message you're currently on (whited out...I wish it stood out even more, btw...bigger font, for one thing), and click on the message below. But you have the sickening feeling that you're gonna have to repeat all that scrolling and hunting in a sec when you're ready to read the NEXT message. It's a LOT of scrolling. A lot of scrolling is not sleek design.
So you hit the "next" button, thinking that's clear enough. Doh! You're in the next thread. W3T doesn't make that clear to you at ALL.
Newbie's have, at this point, pounded their keyboards in frustration. Why, oh why, is it so hard to read the next message in a thread?
Perhaps there's a simple solution I'm missing. If so, there's an interface problem, since the solution is not obvious to me (I'm no tech genius, but am a very experienced BBS user). If there is NOT a solution, this is a BAD thing.
I can envisage a lot of fixes, but rather than list a bunch, I'm hoping to hear responses on this.
chowhound.com
For Those Who Live to Eat
