Bug 13759 - F# hover text does not appear in Xamarin Studio 4.1.7 alpha
Summary: F# hover text does not appear in Xamarin Studio 4.1.7 alpha
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: F# Add-in ()
Version: Trunk
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Dave Thomas
Depends on:
Reported: 2013-08-05 13:18 UTC by James Moore
Modified: 2015-01-27 04:40 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description James Moore 2013-08-05 13:18:53 UTC
Xamarin Studio 4.1.7, OSX

Put the mouse over a variable.  No hover text appears telling you the type.

This worked before the 4.1.7 alpha release.
Comment 1 Dave Thomas 2013-08-05 13:38:22 UTC
I believe Its fixed in the main repo: https://github.com/fsharp/fsharpbinding
Comment 2 Dave Thomas 2013-08-05 13:39:49 UTC
You should raise issues to the Github repo, its open source and not owned by Xamarin.
Comment 3 James Moore 2013-08-05 14:18:33 UTC
I should probably do both.  Part of the reason for filing here is that I'd like Xamarin to be adding F# items to their list of "things that must work before you can ship an alpha" - whether or not the fix is upstream in the github repo shouldn't shouldn't matter for the release/don'tRelease decision.

Plus it's not always clear to me exactly which components are causing any particular problem, so starting with a Xamarin bug seems reasonable.  (I may feel that way just because we gave them money...)
Comment 4 Dave Thomas 2015-01-27 04:40:03 UTC
Fixed as per #C1