Bug 36337 - Hard to navigate between overloads of functions
Summary: Hard to navigate between overloads of functions
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: Roslyn
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2015-11-29 06:59 UTC by Marius Ungureanu
Modified: 2015-11-30 07:04 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 ANSWERED

Description Marius Ungureanu 2015-11-29 06:59:02 UTC
With the new Roslyn completion engine, it's pretty hard to navigate between overloads in completion.

let's say:

> new Action(

Will trigger the completion window with down/right for completion elements, left-right for overloads.

then let's try:

> string.Equals(

Right now, the completion is ok.

But if I write anything, the completion widget appears and the overloads widget both use up/down keys. I think the overloads widget should switch to left/right.

> string.Equals(e

Will break it.
Comment 1 Mike Krüger 2015-11-30 07:04:14 UTC
left/right is used in the completion window for cycling through overloads using that in the overloads window would break that.

I think it's an issue for design.