| Age | Commit message (Collapse) | Author |
|---|
|
Fixed bug #55351 - Dirty file interferes with creating new project
https://bugzilla.xamarin.com/show_bug.cgi?id=55351
With unsaved files open in the IDE, creating a new project would
show a dialog prompt asking to save changes. This dialog had two
buttons Cancel and Save (or Save As). Now the dialog also has a
Don't Save button which will discard the changes and close the unsaved
file. Also the dialog now has a message saying that not saving will
cause the changes to be permanently lost.
|
|
The Invoke API now can take both an Action and an EventHandler. delegate {} causes ambiguous results.
|
|
(fixes bug #57621)
|
|
* [Ide] Remove dead code.
* [Ide] Fix possible de-registrations of unregistered sources.
|
|
Fixed 'Bug 56650 - Many workspace errors logged while coding'
|
|
Tab to cycle through Indicator, Tasks and Usages
Up and down arrow will cycle through the individual tasks and usages when they are focused
|
|
|
|
File move caused a crash because it's not handled properly. That
ensures that the move is handled like a rename in open file case.
|
|
Without a repro it's hard to tell why that happens. This patch should
ensure that no invalid document is open and that the analysis document
invalidates when the roslyn workspace closes the open document. The
source text container has now a check on invalid documents as well and
tries to reopen the document in that case. This should fix the issue.
|
|
dispose.
Had a log that showed that the reparsing is tried on a disposed
editor. Shouldn't happen in the current implementation but I added a
check to ensure that's not happening.
|
|
IntelliSense'
Was just an reopen of the analysis document missing - the underlying
bug was already fixed as a side effect.
|
|
|
|
The tabstrip code was not removing the tabs from the tabstrip list. Fix this by correctly using the events.
|
|
This reverts commit 00879ff951ae13b21ed550e87494e09fe4f78e42, reversing
changes made to 9d302f4978e67538b4fbf6ae4b5353444bb76ab4.
|
|
The tabstrip code was not removing the tabs from the tabstrip list. Fix this by correctly using the events.
|
|
|
|
|
|
|
|
|
|
get "An Autosave file has been found for this file"'
|
|
Fixed 'Bug 55455 - Code completion lost when moving files'
|
|
This reverts commit 5c4c02e4bbd471fd84d1d4626ebcbe136e7364ef.
|
|
|
|
Fixed 'Bug 55476 - TypeSystem task loop'
|
|
Fixed bug #55457 - Issue when trying to create a new project while a
file has changes
https://bugzilla.xamarin.com/show_bug.cgi?id=55457
With a file modified and open in the text editor, selecting New
Solution shows a dialog asking to save the modified file. Clicking the
Save button would then not open the New Project dialog. The problem
was that the Document.Save method returns a task and the code
was checking the Document's IsDirty property before the save
completed which prevented the New Project dialog from being opened.
|
|
|
|
That makes the work around with adding/removing event handlers
obsolete. That didn't really work because the event was triggered on
UI thread.
|
|
This reverts commit 3d45f360025b6388b970aa10c737e2e72d6d0dad.
|
|
|
|
|
|
excluding conditional ItemGroup'
This patch prevents the document in beeing in state Project != null &&
AnalysisDocument == null.
|
|
|
|
breaks IntelliSense'
It was caused by the project wasn't set correctly after save as.
|
|
Remove dead code (parentSolution is never used).
|
|
Fixed 'Bug 53380 - [Webtools] Editor inserts BOMs sometimes'
|
|
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.
|
|
Fixes XBC #54232
|
|
|
|
|
|
Otherwise it will try to find the new document in the old project and fail, causing analysisDocument to be null. And when analysisDocument is null, various language services are turned off.
The symptom was when calling Save As on a .css file completion stopped working. I've verified that after this call is made completion works fine after SaveAs on a .css file.
|
|
|
|
|
|
|
|
Makes AccessibilityElementProxy a wrapper object so that we don't need a XamMac
reference on MonoDevelop.SourceEditor
|
|
|
|
|
|
Await all registered Closing handlers. Awaiting the Event
itself will only wait for last registered handler.
|
|
If a workbench window contains an unsaved document, we ask the user
to save it and run the save operation asynchronously. This is controlled
by the WorkbenchWindowEventArgs.Cancel property and the result
contols whether we set specific Gtk/GLib events as hanled or not
(i.e. in order to allow or disallow Gtk to close a window).
The first problem here was the async EventHandler for the Closing event
which was not awaited and the window was closed before the
Save operation had a chance to run to completion. This is solved by
an EventHandler delegate returning a Task, making it possible to
await the handlers subscribed to the event.
The second problem with this approach was that Gtk doesn't know
anything about awaiting Tasks and if one of its event handlers
leaves the synchronization context (like the asynchrounous
file saving), it will let the signal pass without waiting for its
handled state to be updated. This is solved by delaying window
closing/destruction (always set the initial delete/close event
handled state and close the window in a continuation task
synchronized with the UI thread)
(fix bug #53089)
|
|
|
|
|
