Age | Commit message (Collapse) | Author |
|
It's the rosyln code lens service driving the first code lens.
|
|
This was caused by some old code trying to manage the addition/removal
of line markers. Was a left over of times where line markers weren't
stored in segment trees. I removed the old handling code it was mostly
unused anyways.
|
|
BXC #53783
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixed bug #58392 - Blank Forms App Template Uses C# Language Instead
of Previous Selection
https://bugzilla.xamarin.com/show_bug.cgi?id=58392
The language button selector was not updated when a recently used
project template was selected on opening the New Project dialog. This
resulted in the selected language in the UI not being the language
used when creating the project. Now the language selector is updated
if the language is changed when a recently used project template is
selected.
|
|
|
|
doesn't work if "Show completion list after a character is typed" is
unchecked'
Command broke during API changes for the webtools team. I added a test
for that option.
|
|
Creating a CocoaApp project that targeted Mavericks and then creating
another CocoaApp project that targeted a later Mac OS would then
result in two CocoaApp projects for C# shown in the recent project
templates list in the New Project dialog when they are logically the
same template just part of a group of templates.
|
|
Fixed bug #58412 - Unable to create CocoaApp from recent templates
https://bugzilla.xamarin.com/show_bug.cgi?id=58412
After creating a CocoaApp (Mac - App - General) that targets
Mavericks if the CocoaApp project template was selected from the
recent projects list in the New Project dialog the project would not
be created if a later Mac OS was selected. In the IDE log an error
would be reported:
No template found matching condition 'Yosemite=false'.
The problem was that the selected project template was part of a
group but the group was not selected. When a different Mac OS was
selected for the new project the condition applied would result in
no template being found.
|
|
Fixes BXC #53775
|
|
Fixed bug #11946 - Need a way to export build errors and warnings
https://bugzilla.xamarin.com/show_bug.cgi?id=11946
Allow multiple rows to be selected in the Errors pad. The Copy menu
will be enabled if multiple rows are selected. The Go to and Show
Error Reference menus will be disabled if multiple rows are selected.
The Copy menu will copy all selected rows to the clipboard.
|
|
|
|
Fixed bug #57934 - When adding project to solution "Create a project
directory within the solution directory." checkbox is not respected
https://bugzilla.xamarin.com/show_bug.cgi?id=57934
To reproduce the original bug:
1. Create a new solution using the New Project dialog and ensure
the Create a project directory within the solution directory is
unchecked.
2. Add a new project to the existing solution.
3. The final page of the New Project dialog would have the Create
a project directory within the solution directory check box checked
and disabled. However the project would not be created in its own
directory.
|
|
Added unit tests for the logic of whether the create directory
check box on the final page of the New Project dialog is enabled and
checked before fixing a bug in this logic.
|
|
|
|
[A11y] Ignore the image and arrow of the dropdown button
|
|
|
|
[A11y] Make the New Breakpoint dialog accessible
|
|
|
|
|
|
Stop the error pad resizing column widths constantly
|
|
The error pad is constantly resizing the description column, which causes it to recalculate all the column widths,
update all the texts and strings.
This is playing havoc with the accessibility, even with only two errors shown
Instead of resizing the description column as needed, just set it to expand and give it the full width
|
|
Fixed 'Bug 58219 - Keyword(Access) not working in custom text color
|
|
Fixed 'Bug 58123 - Writing " makes two of characters, but delete only
|
|
The new version of the tool support incrementality, so if the binary is already patched, it won't touch it so the timestamp will remain the same and won't invalidate dependencies unnecessarily.
|
|
theme'
Didn't think there were themes that used the old keyword colors.
They're a direct inheritance of SharpDevelop :). However there isn't
any reason we don't support that in the textmate theme - we still
control that.
|
|
Adds a Diagnostics menu item to put a mark in the log.
|
|
|
|
column mode
|
|
This makes our build more deterministic, without different versions of System.ValueTuple.dll overwriting each other in the output directory.
|
|
[57111][Ide] Fix KeyBindingSet compare with parent Pt. 2
|
|
|
|
[A11y] Improve tabstrip accessibility
|
|
|
|
Now that the whole of the shell UI can be focused, lots of controls like to
steal the keyboard focus meaning that when we expect to be able to type in the
editor, we often can't. To fix this, when opening a new document, we have the
editor grab focus.
|
|
|
|
|
|
mode'
Some highlighting styles were wrong in that highlighting case. Dark &
Light mode are well supported - but some of the lesser used ones
needed attention.
Fixed a minor drawing bug in text link mode as well.
|
|
* fix parent selection for compare
* skip unchanged and empty bindings in schemes
(fixes bug #57111)
|
|
Cleanup MD.Core and MD.Ide references.
|
|
Fix issue in FastCheckNeedsBuild
|
|
This helps avoid unnecessary copy operations during the build.
|