When I finish reading a thread I click on the forum name to exit the thread, but the board isn't unmarking the thread. Am I not exiting the thread properly? Or is this a "Microsoft Feature"? (also known as a bug.)
It would be nice to implement a timestamp marking read all the threads up to the one you are currently viewing but leaving the newer/updated threads unmarked. That helps at least for the folks who only have like a minute or two to view stuff.
That's a really good idea. We could put that on every thread too instead of just the newest thread in the category...
I think there might be an issue though if we don't pass the value to the variable at the time the thread is loaded rather than when you press the button because somoene could put a new post in a thread while you are reading it.
I'm working on something else right now, but I will see if I can make that work tomorrow night (CRZ can probably do it tonight - he did the initial work on putting the mark thread read in the post)
Not to change the topic or anything, but I have a question for you Zims (ignore if you answered it to my posts in TEST) but when I edit my posts, all the {br} returns get deleted from my sig line.... why is this and how can I fix it?
-Jag
"You gotta hate somebody before this is over. Them, me, it doesn't matter."
"Hate, who do I hate? You tell me."
"Who do you love?"
-Wintermute to Case in William Gibson's Neuromancer
I guess the difficulty comes in determining the timestamp itself. Example: Posts 1-10 happened at time A. I read the thread at time B. Someone posts #11 at time C. I mark forum reador mark to here at time D.
Which time gets saved?
In the "Mark to here", I would save time A. In the "Mark forum read", I would save time B.
Well, whatever you decide to do, I'm sure it's appreciated.
EDIT: Oops I forgot that saving time A would affect all those future posts in the newer threads. Nevermind!
(edited by zoggy1 on 17.4.02 1728)
Press [Enter] to exit.
Hit [Escape] to return.
Originally posted by zoggy1Oops I forgot that saving time A would affect all those future posts in the newer threads.
Bingo. That's the problem.
Taking Aaron's example to an extreme:
Let's say it's Monday and you took the weekend off (which everyone should do, ha ha) and you get into "Site Bashing" - there's two threads:
The top thread has ten new articles dated Saturday, Saturday, Saturday, Saturday, Saturday, Saturday, Saturday, Saturday, Saturday and Monday.
The bottom thread has *one* new article, dated Sunday.
Let's say you read that bottom thread and decide you'll hit the other thread later, so you reset the Read time - it would be set to Sunday 'cause that's the timestamp on that last new article.
Oops! NOW when you get around to hitting that top thread, you only see ONE new message instead of ten....and you end up missing 90% of the discussion.
We've been trying to figure out how Delphi does it without some kind of insane database - and we've come to the conclusion that they probably keep some kind of insane database. ;-)
In the end, the best solution for now is to log in frequently, try very hard to avoid making pointless additions to threads, and find your own way to determine what you can read and what you can mark off without bothering to read.
In honour of the Super Bowl, Sec19Row53 suggested building a jersey through the nfl.com site, then using it. Of course, we used the Packers, even though they didn't even come near SNIFFING the playoffs. I'll *probably* decide who to root for by...
Pages: 1
#
