Bug 14078 - HexEditor tries to get negative byte ranges when editor data is too short to fill a page
Summary: HexEditor tries to get negative byte ranges when editor data is too short to ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-08-19 14:44 UTC by Jeffrey Stedfast
Modified: 2013-08-20 03:10 UTC (History)
1 user (show)

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:

Description Jeffrey Stedfast 2013-08-19 14:44:06 UTC
If you use the new HexEditor debugger visualizer, the HexEditor widget tries to get bytes in the <0 range because it positions the hex display of bytes at the bottom of the page in view

You can get to the HexEditor visualizer by viewing byte or sbyte arrays.
Comment 1 Mike Krüger 2013-08-20 03:10:39 UTC
It's the fault of the scroll view.