Longer status line messages: persist until next user click
Apparently the devs can read 'WAYYYyyy faster than I, because status line messages have a tendency to disappear 😒😠😡 about halfway thru my reading them.
There's no reason to erase a status line message until the user is done reading them. Which can be signaled by the next user mouse click.
The user could have looked away. They could have vision issues ( 🙋♂️ ). They might not have known a status line message would be coming, or they might be looking at the wrong monitor. It doesn't matter: if a message is sent, it should stick around for a while.
Tying its erasure to the next user click (not the next mouse movement, that's problematic) is a reasonable measure: some arbitrary time-out is not.
3 Comments
There should also be an 'x' to quickly get rid of it and a copy button that copies the message to clipboard.
* @zorro.weaver * I think that is not so effective, due that error, alert is related with something, and log have more info what need to copy.
I often checking in Script workspace where is logs about. I think the time adjustment option when disaper can be good or by click "close" msg. The problem is more advanced, eg. if Status bar is turned off and messages then are showing up, and if area is divided and exist more than 2, then all is no sense
You can do own are with
Infowindow from down (Log operators)