[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

That tool is presently MIA…

We’ve had enough feedback on the new thread view that we’re going to go back to the old style, and that’s first on our list of things to do today. After that, we’ll see about getting the mark as read feature rebuilt for the new system. It’ll be back fairly soon, but not quite immediately. Just give us a little bit of time. Many people were having issues in general with the way the browsers were marking what posts were read, and we’re eliminating those right now as well. We’re also retuning the cookies themselves right now as well. It’s all just part of what you expect to have happen when you switch servers and mechanisms at the same time. 3 major operating systems, times X different browsers for each… it’s been a while since coding the user interface side was a simple task – there are more different browsing combinations out there than there are people working on the Cow Team – and there are a number of different ways to surf inside the Cow system itself – thread views, date views, summary views, individual posts, whole threads… you get the picture.

All that said, the “Mark as Read” tool will be coming back – we just need a little bit of time to get to it.

Eric Bliss

systems design and integration
CreativeCow.Net

int main(void) {
printf(“Hello World!\n”);
}

[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

[Eric Bliss]

AH!!! I think I see what your problem is… What size is your screen? I’m gonna bet that it’s an 800×600. The present threads interface was designed for use with a 1024 across screensize. Once you shrink it down too far, the browsers start doing weird stuff to it – which is what I think you’re seeing. Try increasing your screen size, and I’ll bet you the problem you’re having will go away.

Eric Bliss

systems design and integration
CreativeCow.Net

int main(void) {
printf(“Hello World!\n”);
}