http://www.winehq.com/site/developer-cheatsheet is 1.5 times as wide as my screen in Firefox and Mozilla. Seems like it needs a bit of adjustment...
Dan Kegel wrote:
http://www.winehq.com/site/developer-cheatsheet is 1.5 times as wide as my screen in Firefox and Mozilla. Seems like it needs a bit of adjustment...
Yes, I frankly think that is a bug in Mozilla/Firefox, but it has been that way for a very long time. The width in the case of the above link is being caused by the string in the +relay section beginning: RtlEnterCriticalSection;RtlLeaveCriticalSection;... To make it display at a more reasonable width, the string needs to be shortened or split up.
On Mon, 15 Nov 2004 08:37:18 -0800, Duane Clark dclark@akamail.com wrote:
Yes, I frankly think that is a bug in Mozilla/Firefox, but it has been that way for a very long time. The width in the case of the above link
Actually, it will render that way in every browser because the line has no break in it. Attached patch is probably the easiest way to fix it. I think we can assume anyone reading this doc is intelligent enough to put it all on one line.
-Brian
Brian Vincent wrote:
On Mon, 15 Nov 2004 08:37:18 -0800, Duane Clark dclark@akamail.com wrote:
Yes, I frankly think that is a bug in Mozilla/Firefox, but it has been that way for a very long time. The width in the case of the above link
Actually, it will render that way in every browser because the line has no break in it. Attached patch is probably the easiest way to fix it. I think we can assume anyone reading this doc is intelligent enough to put it all on one line.
-Brian
Well, okay maybe bug is the wrong word. But I see it all the time, for example when looking at msdn.microsoft.com, and it is rather annoying. It seems to me that just because there is one object on the page that is wider than the browser window, that is no reason to render everything that wide. Then again, I'm not the one writing the code... :-)
On Mon, 15 Nov 2004 09:39:10 -0800, Duane Clark wrote:
Well, okay maybe bug is the wrong word. But I see it all the time, for example when looking at msdn.microsoft.com, and it is rather annoying.
Yeah, but I wouldn't judge anything by looking at MSDN, it routinely feeds broken IE specific HTML to Mozilla.
On Mon, 15 Nov 2004 08:37:18 -0800, Duane Clark wrote:
Yes, I frankly think that is a bug in Mozilla/Firefox, but it has been that way for a very long time. The width in the case of the above link is being caused by the string in the +relay section beginning: RtlEnterCriticalSection;RtlLeaveCriticalSection;... To make it display at a more reasonable width, the string needs to be shortened or split up.
It's not a Gecko bug, I'm pretty sure of that, it's just me sucking.
The real fix is for everybody to by flat screens and use 1280x1024 screen resolutions, but a quick hack would be to insert some spaces into that string so line breaks can be inserted. I think the following patch should help.
Index: developer-cheatsheet.template =================================================================== RCS file: /home/wine/lostwages/templates/en/developer-cheatsheet.template,v retrieving revision 1.1 diff -u -p -r1.1 developer-cheatsheet.template --- developer-cheatsheet.template 10 Nov 2004 00:20:10 -0000 1.1 +++ developer-cheatsheet.template 15 Nov 2004 17:04:06 -0000 @@ -75,7 +75,7 @@ in the [Debug] section if you're being overwhelmed by certain functions. A good initial value for RelayExclude is:<p>
- <code cols="72"> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel;_LeaveSysLevel;_CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap;LOCAL_Lock;LOCAL_Unlock </code><p> + <code cols="72"> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel; _LeaveSysLevel;_CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap; LOCAL_Lock;LOCAL_Unlock </code><p>
Most of these functions are called a lot, but don't usually give any clues as to why a program might be failing. <p>
-
Brian Vincent -
Dan Kegel -
Duane Clark -
Mike Hearn