Using link in quickinfo markup

This one is a little tricky. In terms of mouse interaction with the QuickInfo, there are three places:
1) OnMouseHover
2) OnMouseMove
3) OnMouseLeave

It seems like you would need to turn off the OnMouseMove and OnMouseLeave portions. The problem with turning off OnMouseLeave is that if you move outside of the SyntaxEditor control then the quick info would still stay up. If we leave the OnMouseLeave code in place then it doesn't hide the quick info until you move the mouse over the quick info (since it's a different window than SyntaxEditor).

So with those things in mind, I'm not sure what the best way to handle this is. Any ideas?

Good news, I was able to find a workaround for the mouse leave issue described above. So the next maintenance release will have this new feature:

Added the IntelliPromptQuickInfo.HideOnMouseMove property, which when false will not hide the quick info until the mouse hovers over another part of the SyntaxEditor or leaves the SyntaxEditor control or quick info tip.

Awesome, I look forward to giving it a try. I'm not sure what you mean by "another part of the syntaxeditor control?" Do you mean any other token other the one we're interested in, or do you mean margins, gutters, etc?

My own best guess would have been to introduce a small delay between moving off the token and hiding the quickinfo, giving the user enough time to get onto the quicklink. But if your fix gives the functionality I'm looking for without having to introduce that complexity, I couldn't be happier.

Thanks!
Jared

Yes, that means if the mouse hovers (with delay) over another part of the editor like a token or column, etc.

I think the new property handles your scenario perfectly. As long as the end user moves the mouse to the quick info tip without stopping and hovering, it will work great.

OK Great I look forward to giving it a try. Thanks!

Jared

Hmmmm...That's definitely the UI effect I was after, but the SyntaxEditor.IntelliPromptTipLinkClickEventHandler was never fired. Does it work for you?

I suspect that the code to hide the tip on mouse click is interfering with the code to fire the event on link click.

Thanks!
Jared

Thanks it looks like a LostFocus handler was closing the tip before the link click could process. This is resolved in the next maintenance release for when HideOnMouseMove is false.