As I mentioned on another topic, suggestions for improvements and wishes for new fuctionality
do get passed on to admin.
Not everything is "do-able" bearing in mind that we have to work with the resources we have
now (hardware, software, firmware) and not with what we would like to have.
I also said on the other topic that all requests need to be considered in terms of performance. As an example, here is some general information to Newf's enquiry about "mark all as read":
To do this, the software needs to create a matrix of topics/members. Every time a member reads a topic, the topic is marked as read
for that member. Any time somebody adds something to the topic, that topic must now be marked as "unread" for
all members (apart from whoever actually posted the new reply
- we've had this discussion before:
Topic: What does "new" by a posting mean ?
http://www.rootschat.com/forum/index.php/topic,127304.0.html )
I don't know how the software could best do it:
1) a "matrix" file, as above ?
2) every topic in the database has a list of members "attached" that needs constantly setting and resetting ?
3) every profile has a list of "topics read" attached, that needs constantly setting and resetting ?
Part of this in place already (otherwise we couldn't have the "Show unread posts since last visit." link) but to do this for every member and every topic is an aweful lot of work.
I'm not saying it can't be done, and I'm not saying it won't be done;
I'm merely trying to show that there is sometimes quite a lot of work behind what seems like a simple task, and that some of this work can also mean performance loss.
Bob