This should exist. I hate when the message number pops up even after I look at them! It makes me think there are new messages, only to find out the same ones are still there. Please add this!

when green flag clicked
ask [Mark all messages as read?] and wait
if <(answer) = [Yes]> then
Mark all messages as read
end

I'd like the button too! (support)

Same! I support!

Support, it stresses me out when I see too many messages in Messages.

k0d3rrr wrote:

Support, it stresses me out when I see too many messages in Messages.

I'm glad to hear that!!!

This would be an amazing feature - i never find myself able to remove that pesky orange circle 1st try, it always takes a bunch of clicks to finally get it off.

That isn't such a bad idea, here's a mock-up I made really quickly (tell me if there's anything you want me to change):

DUPEM! be careful not to necropost, make sure you are adding to the
suggestion

Scratch_NT wrote:

I'd like the button too! (support)

-MeowTheCat- wrote:

Same! I support!

Please explain why you support it. In the suggestions forums, constructive posts matter more than the number of supports.

My reasoning: I feel like many people have a bunch of messages, and want to get rid of them. This could help them out. Another reason:

7salad3salad wrote:

This would be an amazing feature - i never find myself able to remove that pesky orange circle 1st try, it always takes a bunch of clicks to finally get it off.

Support! This would help me after I go on vacation and have 300 messages of studio activity…
I can feel my OCD going away…

It can be quite annoying, I'd support such efforts. Or, some sort of better detecting function that ensures when you go the messages tab it counts it?

Either way, nice idea, would definitely help with sorting messages and knowing that you've received something new instead of it showing the same old notif.

Support because it's annoying to read my messages then have them still unread so I read them again.

Bump

bump dupe

dupe happened so bringing up

Zydrolic wrote:

dupe happened so bringing up

This topic is a duplicate of this one: https://scratch.mit.edu/discuss/topic/249790/, so discussion should continue there.

KangaCoder wrote:

(#16)

Zydrolic wrote:

dupe happened so bringing up

This topic is a duplicate of this one: https://scratch.mit.edu/discuss/topic/249790/, so discussion should continue there.

Ah alright.
Apologies then