Bug 2069 - Completion tooltips do not show up on incomplete lines
Summary: Completion tooltips do not show up on incomplete lines
Status: RESOLVED DUPLICATE of bug 3468
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
URL:
: 2070 ()
Depends on:
Blocks:
 
Reported: 2011-11-16 18:36 UTC by Alan McGovern
Modified: 2015-08-20 03:24 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 3468

Description Alan McGovern 2011-11-16 18:36:42 UTC
for example:

var f = new List ().Select (x => x.Y).Where (f => f.Foo == bar)

Here if i type a '.' on the end of the line i do correctly get completion telling me what is available, however if I hover over the 'Where' statement with my mouse, it does not give me any tooltip. I have to put the semi-colon on the end of the line before the tooltip will appear.
Comment 1 Mike Krüger 2011-12-08 06:58:17 UTC
*** Bug 2070 has been marked as a duplicate of this bug. ***
Comment 2 Mike Krüger 2012-02-23 01:59:27 UTC

*** This bug has been marked as a duplicate of bug 3468 ***