Bug 11437 - Global search shows "no matches" on typing colon
Summary: Global search shows "no matches" on typing colon
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-03-26 18:12 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-03-27 05:53 UTC (History)
1 user (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 Mikayla Hutchinson [MSFT] 2013-03-26 18:12:26 UTC
If I just type : in the global search shows "no matches" which is a bit confusing. IMO it should not show the popup at all, or show a hint to the user to type a line,col.
Comment 1 Mike Krüger 2013-03-27 05:53:12 UTC
I see you really, really want this feature :)

I'm still not sure if it is a good one - we've goto line number function as part of the text editor widget. The global search entry isn't really the right place for it.

We can only do it because we're not supporting floating windows like VS.NET - if we decide to 'clone' the main window like xcode does we can do it. But still the inline goto line number widget works for embedded source editor controls (like in the assembly browser).

It's feature duplication which should be avoided. But in that case I can't find any good reason for not doing it. But when choosing a 'floating window' model we need to be careful. (Not just because of this feature - I'm sure there are more)