Annoying hover effect

Bug Reports Studio Bugs
,
1

I have been using next gen studio for a little while now and this has been a reoccurring issue. I’m not entirely sure how to replicate it but this has been a frequent occurrence. I’ll hover over a random button, it will tell me what it does, but the hover description doesn’t go away when it’s supposed to. I can be on an entirely separate window and it will overlay it.

7 Likes
2

Have been having this issue since the release despite multiple attempted fixes from engineers. Would be nice to get a status update on this, seems like quite a low priority issue which is unfortunate @MeshOfPaul

3 Likes
3

We are still fiddling with tooltips! We had a good conversation about it last week when we were bug bashing the upcoming playtest and customization UI updates. Some of it is just the timing logic needs more refinement. But there’s also some known issues caused by the things we have to do to play nice with Qt.

5 Likes
4

I’ve been paying attention to it a lot now, and it seems like it comes up the most when entering/exiting a playtest in studio.

2 Likes
5

This just occurs when you unhover very quickly, I get it always when I either tab out or close something.

2 Likes
6

I was thinking of making my own bug report for this but I’m sure it’s related, so I’ll post this here.

Repro:

  • Have the ribbon bar undocked.
  • Hover over the ribbon bar.
  • Start a playtest. Ribbon bar will not disappear, instead it will persist until you hover over and exit again.
  • Stop the playtest and tab out. Ribbon bar will display over other windows in your desktop.
1 Like
7

You can also just hover over a button, wait for the tooltip to show, then quickly hover over another one and it’ll be guaranteed to stick.

Kinda has the same vibe as the bug where “MouseLeave” event would not always trigger correctly. I think it has something to do with moving your mouse into the center while the tooltip is up.

2 Likes
8

I think its just an issue with DockWidgetPluginGui:GetRelativeMousePosition(), it completely stops working when you exit the widget (which i assume is intentional) but imo this is probably the reason as to why this is so hard to fix, Roblox needs to rework their whole damn edit-time input detection to fix it (which is good, it f###### sucks)

1 Like