Bug 190 - "Place array initializers on new line" does not work
Summary: "Place array initializers on new line" does not work
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Low normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-08-05 03:15 UTC by Alan McGovern
Modified: 2015-08-20 03:24 UTC (History)
2 users (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 FIXED

Description Alan McGovern 2011-08-05 03:15:41 UTC
Changing from "Always on same line" to "always on new line" has no affect on the sample code.

Also this option could be change to a simple checkbox instead of a dropdown.
Comment 1 Miguel de Icaza [MSFT] 2011-08-30 11:50:32 UTC
Setting to Resolver branch, to ensure this gets fixed then.
Comment 2 Mike Krüger 2011-12-14 06:26:58 UTC
fixed.

The formatting engine got rewritten for the new ast at one point, therefore some options got forgotten.
That happened a long time ago, after that some options got added to the 'old' engine and not transferred to the new one - that happened for example for this option - it's really about time to end the fragmentation of the ast/type system/formatting etc. and focus on one branch :)