Mouseover text binding in template blocks Mouse Entered script from running

Thank you for the additional info!

I've found that I had the same issue if the mouseover binding was on the same component as the mouseEntered script. Seems like the mouseover binding takes precedence and then there's nothing set up to queue the script to run after the mouseover text is displayed.

It looks like something similar has been mentioned in the forums and in our support tickets. According to our engineers and others in the community, this is expected behavior for any Java swing application.

Sorry, I know it's not ideal, but a potential workaround is to set up the mouseover text binding on a component inside of the template. When I set it up on a label inside of the template, I noticed that when my mouse entered the template, the script ran, then when it went over the label, I saw the mouseover text, then when it left the label, it ran the script again as though I wasn't already inside of the template.