Bug 2918 - Rendering issues in assembly browser
Summary: Rendering issues in assembly browser
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Assembly browser ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-01-16 17:04 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-01-23 06:56 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 Mikayla Hutchinson [MSFT] 2012-01-16 17:04:52 UTC
The assembly browser has some issues.

a) there are "gaps" at the end of each line when the text is selected
b) the link underline is the text color but does not change when selected
c) the link underline is fuzzy, placed 0.5px off the vertical line
d) There are superfluous underlines on (,) punctuation

Comment 1 Mike Krüger 2012-01-23 06:56:55 UTC

Btw. can you open bugs more individually next time? Makes commits easier to read & if a bug in a list is hard to fix it's better to track them individually

a + b/c + d for example.

- A affects the whole text editor btw. - I managed to repro it with a certain font in the text editor as well.
- B+C the underline markers general (error/warning underlines!)
- D is indeed assembly browser specific

According to this I would value them differently A high, B+C normal, D is more low - (when the ILSpy decompiler is upgraded to the new type system I suspect that it'll vanish from alone).