Hi,
When i am crusing the help files I keep running into sections of text that have overlaped in the display.
When i am crusing the help files I keep running into sections of text that have overlaped in the display.
Is it just me (MyVidCard) or has anyone else come across this, or do you know the fix
Thanks in advance for any help.
Steve

Text Lines OverLaps in the Help Menus Display Window
Sime24
RedAlarm
enet2008
Great, Thanks for the help and the reply.
Raul Mendoza
Grant Hodson
This is a bug in MSDN Online, and the fix should be rolled out in the next couple of weeks. So after Feb. 15 or so you should not see this problem any more.
Michael Blome - Visual C# Documentation Team
Nabeel Akhtar
poderosa
Thanks for getting back to us. I've been able to reproduce the problem here.
No, there's no new Java requirements. This just appears to be a text rendering bug. We'll look into getting it fixed for future versions of the document viewer.
pjks100
I expect there are two reasons why this wasn't reported during beta:
1. The final documentation came in very late during the beta cycle, and in fact there were warning notes at the top of the beta documentation saying that it was not final.
2. The overlapped rendering bug is exposed by some specific layout tags used on the help content. My guess (although I haven't researched it) is that these tags weren't present on earlier builds of the documentation.
Karl Sumwalt
Can you tell us what video card you have and what driver you're using You can get this information from the Advanced tab on Display properties (right click on the desktop and select Properties, or get to the same UI via the Control Panel)
Also:
1. Are you using online help or local help
2. Are you viewing help within the Visual Studio IDE or in the external "Microsoft Document Explorer"
3. If you copy and paste the URL from the help page and paste it into Internet Explorer's address box, do you see the same corruption
4. Can you give us the URL as an example of one of the pages that is corrupted (The link you put in the original post was to a local file on your machine, so no-one else can read it).