Bug 46580 - Runtime errors display position but no ability to navigate to error
Summary: Runtime errors display position but no ability to navigate to error
Status: CONFIRMED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger (show other bugs)
Version: 6.1.1 (C8SR0)
Hardware: PC Mac OS
: Low enhancement
Target Milestone: Future Cycle (TBD)
Assignee: David Karlaš
URL:
Depends on:
Blocks:
 
Reported: 2016-11-08 15:48 UTC by Rod Barnes
Modified: 2017-09-01 14:30 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Screenshot showing intentionally added typo and resulting dialogs (614.72 KB, image/png)
2016-11-08 15:48 UTC, Rod Barnes
Details

Description Rod Barnes 2016-11-08 15:48:39 UTC
Created attachment 18380 [details]
Screenshot showing intentionally added typo and resulting dialogs

When a runtime error is encountered in a solution, it displays an error and its position.  However, there is no means to navigate to the location of the error.  The user must manually open the file and location the position of the source of the error.  It should allow a double-click, a link, something that would open the file and place the cursor on the location of the error.  I mean, it knows the position so it should be able to navigate there.

Note You need to log in before you can comment on or make changes to this bug.