Amended on Wed 29 Aug 2012 01:07 PM (UTC) by Fiendish
Message
The difference is that MUD output scrolls without user input constantly under normal conditions, whereas few other things do. I don't believe the two situations are analogous. Anyway it was just a thought. The miniwindow thing is the real issue.
I've been experimenting with a few other apps and I'm not sure this is expected behaviour. If you bring up something which causes a tooltip to appear, and then scroll using the keyboard (not moving the mouse in other words) the tooltip disappears but is not replaced by a tooltip for the new thing you scroll under the mouse.
Amended on Tue 28 Aug 2012 11:53 PM (UTC) by Fiendish
Message
Actually, now that I think about this again...
I don't think scrolling should ever directly remove a tooltip.
It should just evaluate the mouse position again and load new tip data if appropriate. That way miniwindow tips persist, and output tips have current information. I see no reason to leave the user in an untipped state based on events beyond user control.
I was just going to add that this also affects my stuff as well. It's annoying to have to move off of and back onto hotspots trying to see what the tooltip info is, when mud text is scrolling.
If mousing over a hotspot with a tooltip, a nice message bubble appears. If new data arrives from the server, the tooltip bubble disappears unexpectedly. This can lead to having the bubble repeatedly only appear for a fraction of a second while the user mouses in and out and in and out to get it to come back and stay for long enough to read.
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.