Bug 4591 - ctrl-space doesn't offer correct completion options in object initializers
Summary: ctrl-space doesn't offer correct completion options in object initializers
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-23 04:39 UTC by Marek Habersack
Modified: 2012-04-26 08:43 UTC (History)
2 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 Marek Habersack 2012-04-23 04:39:26 UTC
The screencast at http://screencast.com/t/Vlev2cJ7 shows the issue.

The completion popup shows global types/kewords instead of the members of the object being instantiated.
You can repro it by opening the MonoTouch.Dialog.sln solution from https://github.com/migueldeicaza/MonoTouch.Dialog and then opening the Samples/DemoElementApi.cs file. Ctrl-space fails in any of the nested RootElement initializers.
Comment 1 Marek Habersack 2012-04-23 08:03:16 UTC
The behavior was the same for collection and object initializers. Current master seems to work with the latter, the former is still broken
Comment 2 Marek Habersack 2012-04-23 08:04:29 UTC
Ideally, the collection initializer should offer for completion only known types that can be used to populate the collection
Comment 3 Mike Krüger 2012-04-26 08:43:05 UTC
The exact context isn't possible since these two syntax constructs can't be mixed.
I think it's a valid request that these can be mixed - and maybe a gap in the c# standard. If it gets closed or not it's another story.

But I got around 5 red unit tests out of this context :) - they're now fixed.