| Age | Commit message (Collapse) | Author |
|---|
|
* Implemented void SetupAccessibility ()
* FIndingInFileDialog Accessibility changes .
* Update FindInFilesDialog.cs
* Update FindInFilesDialog.cs
for -> to
* Line brakes changed
* deleted 4 empty lines
* removed empty lines
* Empty lines
|
|
The Invoke API now can take both an Action and an EventHandler. delegate {} causes ambiguous results.
|
|
Value cannot be null error'
Not exactly sure why document.FileName was null. I would've guessed it
was a new empty unsaved file use case - but the screenshots doesn't
look like so. Anyways in the search in open documents use case it's
not needed to look at the file name at all - so that should fix that
issue. But I hadn't any use case for that.
|
|
dialog'
Without the multi line option only string start & end will be taken as
^ or $.
|
|
This avoid allocating strings on mouse movement. There is no way at the moment to get rid of the byte buffer.
|
|
The find in files operation could add BOMs.
|
|
|
|
If someone accidentally uses this field instead one
of the gtk data funcs at least it will contain the
correct object now.
Before this change the treeview would update as soon
as the new model was set, which meant there was a time
where `treeviewSearchResults.Model` and `store` were
different objects.
|
|
We should use the Model we're provided, not an arbitrary
model from somewhere else. They will not always be the
same thing!
Fixes a null ref on this line as the GetValue call
returned null because the iter was part of another
model:
`bool didRead = (bool)model.GetValue (iter, DidReadColumn);`
|
|
In old versions we used a bool to determine if a BOM could be written.
The new editor structure just uses the encoding which can control if a
bom is emitted or not. The text file utility for auto detection now
correctly gives back the right encoding. The bool for the BOM was
removed - it's no longer in the text interfaces as well. Doesn't make
sense to have that on the low level API.
|
|
* [Core] Remove superfluous ToCharArray.
* [Perf] Optimize StringBuilder usage
Go through StringBuilder.Append(string) and StringBuilder.Append(object)
usages. As follows, we no longer concat strings before appending to a
stringbuilder, and we no longer box valueTypes which go through
Append(object).
* [Perf] Optimize StringBuilder.AppendLine
Most notable improvements are in AssemblyBrowser and Diff calculation.
* Fix feedback.
|
|
Conflicts:
main/external/mono-addins
main/src/addins/MonoDevelop.SourceEditor2/Mono.TextEditor/Gui/TextViewMargin.cs
main/src/core/Mono.TextEditor.Shared/Mono.TextEditor.Utils/ImmutableText.cs
main/src/core/Mono.TextEditor.Shared/Mono.TextEditor/Document/TextDocument.cs
main/src/core/MonoDevelop.Core/MonoDevelop.Projects.MSBuild/MSBuildProjectService.cs
main/src/core/MonoDevelop.Core/MonoDevelop.Projects/Project.cs
main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/Document.cs
version-checks
|
|
* [Core] Async/await optimizations
Remove async/await where not needed.
Add ConfigureAwait for all awaits inside a Task.Run or wherever a method already did it.
* [Ide] Async/await optimizations
Remove async/await where not needed.
Add ConfigureAwait for all awaits inside a Task.Run or
wherever a method already did it.
* [Core] Add matching assert to Workspace.Build as Clean has one.
* [Core] Address feedback to 764e103fdc90288b0f56abafccbf95819b175200
* [Core] Address feedback to 764e103fdc90288b0f56abafccbf95819b175200
* [Core,Ide] Address feedback from PR.
* [Core, Ide] Revert async -> non-async conversion for methods which have throw statements.
* [Ide] Address feedback from PR.
|
|
Conflicts:
main/external/mono-addins
main/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/SourceEditorView.cs
main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Editor/TextEditor.cs
version-checks
|
|
from cs files '
|
|
|
|
|
|
definitions aren't syntax highlighted'
|
|
|
|
This reverts commit 5e7c6616171106867f7fdf52ef1526e0c3dcb6e6.
|
|
|
|
token cancellation.
The SearchProgressMonitor always has an attached cancellationtokensource, due to the cancel button in the associated result pads.
The StatusProgressMonitor's cancellation token was not registered to cancel the search one, so the statusbar button did nothing.
|
|
|
|
This is not a good thing to do. The user wants to search in the files in the solution pad, not whatever generated code is done in intermediate output directories.
This fixes a huge performance issue caused by reloading the whole solution while doing find in files.
|
|
|
|
|
|
It's a better name.
|
|
Improve propagation of error messages up to the message dialogs.
Fixes bug #37648 - Opening Workspace (.mdw) - Unknown file format
(solution name not displayed)
|
|
Old SyntaxModes == New SyntaxHighlighting so this is for consistency.
|
|
StringBuilder.Append(string, int, int) wherever possible.
|
|
|
|
previous cursor position if the new edit adds a newline before the old
cursor position'
|
|
Bold doesn't work in all cases & background modification looks better
anyways.
|
|
[Ide] Implement cancellation via status bar.
|
|
|
|
|
|
* [IDE] Improve FindInFiles speed
A context switch to the main thread happens for every file to check if the IDE has the document open already.
Instead batch them together so only one context switch happens.
* [IDE] Speed up FindInFiles
Use Parallel.ForEach to generate the list of files that need to be searched.
* [IDE] Make GetDocumentReaders threadsafe
If we make GetDocumentReaders threadsafe by locking access to the documentsByFilePath variable then we can
remove the need to switch to the main thread.
* [IDE] Remove unused method and don't use dictionary for finding open documents
|
|
|
|
|
|
this call is not supported '
Unfortunately it's not possible to fix that in all occassions (regexes
only work on strings - not streams).
|
|
|
|
|
|
Added focusing the Result Pad on clicking the close button in the
window titlebar.
Removed focusing of the result pad when no results are returned.
|
|
|
|
(fixes bug #37577)
|
|
|
|
|
|
|
|
|
|
Use UTF8 instead of Default to prevent 'strange' code page encodings
on windows. UTF8 is better for cross platform development.
|
