Bug 5857 - Typing Too Fast Results In Invalid DocumentLocation
Summary: Typing Too Fast Results In Invalid DocumentLocation
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.8.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-06-25 17:52 UTC by oldbushie
Modified: 2012-06-26 09:50 UTC (History)
1 user (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 oldbushie 2012-06-25 17:52:27 UTC
I've been getting this error 10 times a day with the Outline enabled, and 2-3 times a day with the Outline disabled. It is VERY disruptive to my workflow. I don't know if I'm typing too fast or what. I've even had it happen after opening MonoDevelop from Unity, clicking in the text editor, and hitting enter twice in rapid succession. I'm stuck using the version of MonoDevelop packaged with Unity since it gives me access to all the correct libraries for autocompletion.

System.ArgumentException: invalid location: [DocumentLocation: Line=200, Column=0]    at Mono.TextEditor.Caret.set_Location(DocumentLocation value) in c:\BuildAgent\work\6b3beae2de4b9011\monodevelop\main\src\core\Mono.Texteditor\Mono.TextEditor\Caret.cs:line 80    at Mono.TextEditor.TextViewMargin.MousePressed(MarginMouseEventArgs args) in c:\BuildAgent\work\6b3beae2de4b9011\monodevelop\main\src\core\Mono.Texteditor\Mono.TextEditor\TextViewMargin.cs:line 1612    at Mono.TextEditor.TextEditor.OnButtonPressEvent(EventButton e) in c:\BuildAgent\work\6b3beae2de4b9011\monodevelop\main\src\core\Mono.Texteditor\Mono.TextEditor\TextEditor.cs:line 932    at Gtk.Widget.buttonpressevent_cb(IntPtr widget, IntPtr evnt)
Comment 1 Mike Krüger 2012-06-26 03:43:02 UTC
Doesn't happen in a more recent md version anymore.

The 2.8.x line is very outdated - it's unfortunate that unity ships with it :(
Comment 2 oldbushie 2012-06-26 08:56:02 UTC
I guess I'll just hope that Unity 4.0 comes with a more recent version then. :/
Comment 3 Mike Krüger 2012-06-26 09:38:32 UTC
I hope so too - the 2.8.x line is very old. I checked the source code - that case is handled now.
Comment 4 oldbushie 2012-06-26 09:50:06 UTC
Well, it looks like it's possible to just open the Unity-generated sln file with the latest MonoDevelop, so I'm doing that for now. The "Sync MonoDevelop Project" option in Unity appears to update the sln file manually so that I get all the latest references, and the sln file does refer to the appropriate Unity dlls. Annoying, but workable for now. I'm just puzzled why they're so out of sync with the current version of MonoDevelop.

I must say, I like the new look. :D