Reply to thread

Message

<blockquote data-quote="and-81" data-source="post: 77639" data-attributes="member: 11844">Possible fixesI've tracked down the problem.&nbsp; Well, for me at least.It seems to me that when MP loads it creates bitmaps of the fonts that are used by the current skin, if they don't already exist.&nbsp; BlueTwo requests Arial, Courier New and Dingbats.When the bitmap is being created MP gets GDI+ to draw each character in the font onto a graphics context.&nbsp; One at a time.&nbsp; Like this:for (char c = (char)_StartCharacter; c &lt; (char)_EndCharacter; c++)&nbsp; ...Now, the problem occurs when it starts processing dingbats and gets up to &quot;c = 127&quot;, because there is no character 127 in the dingbats font I have.&nbsp; GDI+ throws a rather useless exception and the whole thing goes off the rails.I've found two possible solutions:1. Delete the dingbats font.&nbsp; Which works for me, and I've asked mike061960 to try as well and get back to me on.or2. Make a change to MediaPortal.GUI.Library GUIFont.cs to catch the GDI+ exception and skip over any characters that cause it.&nbsp; I've attached my modified GUIFont.cs file to this post for consideration.&nbsp; The change is in the PaintAlphabet method at the end of the file.I'd like to be a bit smarter about it and actually detect when the font doesn't contain a particular character and avoid calling the DrawString operation that causes the exception, but I've searched high and low and haven't found a way to do that yet.&nbsp; In the meantime this looks like a reasonable fix to me.Also worth noting, My HTPC which has been running MP happily for a very long time now doesn't have the dingbats font installed.&nbsp; It's been rebuilt a couple of times over the years and is currently running XP Pro SP2 + Updates.However, BlueTwo uses dingbats in two places.&nbsp; BasicHome.xml and mytvFullScreen.xmlBut here is a list of Windows XP fonts (probably a good resource for skinners):<a href="http://www.microsoft.com/typography/fonts/winxp.htm" target="_blank">http://www.microsoft.com/typography/fonts/winxp.htm</a>Notice, there is no dingbats.Looking at the properties of the dingbats font I found this:&quot;Copyright URW Software, Copyright 1997 by URW&quot;(PM me if you want more &quot;info&quot; on the font)So should BlueTwo be requesting this font if it's not a standard WinXP font?Sorry for the long post.&nbsp; Just trying to get in all the details.Hope that helps.Cheers,</blockquote>

[QUOTE="and-81, post: 77639, member: 11844"] [b]Possible fixes[/b] I've tracked down the problem. Well, for me at least. It seems to me that when MP loads it creates bitmaps of the fonts that are used by the current skin, if they don't already exist. BlueTwo requests Arial, Courier New and Dingbats. When the bitmap is being created MP gets GDI+ to draw each character in the font onto a graphics context. One at a time. Like this: for (char c = (char)_StartCharacter; c < (char)_EndCharacter; c++) ... Now, the problem occurs when it starts processing dingbats and gets up to "c = 127", because there is no character 127 in the dingbats font I have. GDI+ throws a rather useless exception and the whole thing goes off the rails. I've found two possible solutions: 1. Delete the dingbats font. Which works for me, and I've asked mike061960 to try as well and get back to me on. or 2. Make a change to MediaPortal.GUI.Library GUIFont.cs to catch the GDI+ exception and skip over any characters that cause it. I've attached my modified GUIFont.cs file to this post for consideration. The change is in the PaintAlphabet method at the end of the file. I'd like to be a bit smarter about it and actually detect when the font doesn't contain a particular character and avoid calling the DrawString operation that causes the exception, but I've searched high and low and haven't found a way to do that yet. In the meantime this looks like a reasonable fix to me. Also worth noting, My HTPC which has been running MP happily for a very long time now doesn't have the dingbats font installed. It's been rebuilt a couple of times over the years and is currently running XP Pro SP2 + Updates. However, BlueTwo uses dingbats in two places. BasicHome.xml and mytvFullScreen.xml But here is a list of Windows XP fonts (probably a good resource for skinners): [url]http://www.microsoft.com/typography/fonts/winxp.htm[/url] Notice, there is no dingbats. Looking at the properties of the dingbats font I found this: "Copyright URW Software, Copyright 1997 by URW" (PM me if you want more "info" on the font) So should BlueTwo be requesting this font if it's not a standard WinXP font? Sorry for the long post. Just trying to get in all the details. Hope that helps. Cheers, [/QUOTE]

Verification