Bug 2794 - Scrolling through overloads is inconsistent/confusing
Summary: Scrolling through overloads is inconsistent/confusing
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-01-09 09:58 UTC by Alan McGovern
Modified: 2012-10-25 03:31 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 Alan McGovern 2012-01-09 09:58:34 UTC
Pressing left/right while the completion window is open normally scrolls through all available overloads. If there is only one overload for a method, pressing left/right ends up closing the completion list and moving the cursor forwards, normally to the next line. This is irritating as it is not what would be expected.

Can we change the behaviour to either scroll the available overloads if there are some or simply do nothing if there are no overloads.
Comment 1 Mike Krüger 2012-01-10 02:22:22 UTC
No ... this was requested - that was the behaviour before. I said at this time it is inconsistent, but got overvoted :(
Comment 2 Mikayla Hutchinson [MSFT] 2012-01-10 14:27:24 UTC
I think the problem is that we're using left/right for cycling through overloads. We should find a better way to do that, perhaps even getting rid of the need to manually choose between them by displaying them all in a single tooltip (and coalescing similar overloads to appears as default parameters?).
Comment 3 Alan McGovern 2012-01-10 20:56:47 UTC
When trying to figure out a better way of implementing this, look at various methods on the Convert class. For example Convert.ToInt32 () has 19 overloads, 16 of which have just one parameter.
Comment 5 Mike Krüger 2012-10-25 03:31:55 UTC
For some reason we scrapped the idea of a 'show them all' in this phase :/
(I wanted it)

closing this issue, it's a design decision