tag:blogger.com,1999:blog-5638372.post112644064003887938..comments2023-10-10T05:22:56.347-05:00Comments on binkley's BLOG: Pointing fingersBrian Oxleyhttp://www.blogger.com/profile/06617364377560752378noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5638372.post-1126449096591558082005-09-11T09:31:00.000-05:002005-09-11T09:31:00.000-05:00Happiness... the developer whose comment I quoted ...Happiness... the developer whose comment I quoted replied. :)<BR/><BR/>I'm trying out Mustang b51 this morning to confirm that it fixes the problem. If so, I'm going to see how much work it is for me to back port the fixed class(es). If it works out easily, I'll post a JAR and instructions for gluing it into a default installation of IDEA.Brian Oxleyhttps://www.blogger.com/profile/06617364377560752378noreply@blogger.comtag:blogger.com,1999:blog-5638372.post-1126448796576977702005-09-11T09:26:00.000-05:002005-09-11T09:26:00.000-05:00Well, in this particular case we could indeed surr...Well, in this particular case we could indeed surround work with Font (like querying infos, drawing, etc.) by building some inhouse wrapper around. But:<BR/>1. It will most probably help anyways since there numerous reports JVM crashes in native code trying to deal with these fonts (we'll hardly be able to work that around, right?)<BR/>2. Walking this way further will require to build a wrappers around _every_ thrid party code including both JDK and libraries and IDEA plugins. Isn't that silly? I mean some people asking something like: yes, I have buggy plugin installed but shouldn't IDEA itself be fault tolerant in this case?<BR/><BR/>Anyway... thanks, we'll try to get that around. No promises though.Anonymousnoreply@blogger.com