[Qt-interest] Problems with Valgrind and Qt / QWS (*NOT* memory "leaks")

[Atlant Schmidt]

Konrad:

> The font rendering problems were solved in one of the early 4.7's.

  Some were, some weren't. One I discussed recently on
  this list (display corruption when a the mmap'd QPF
  file crosses a memory mapping page boundary) wasn't
  fixed in the latest 4.7.x that I had looked at and
  so far, nothing has been done by the Trolls with the
  patch that I submitted.

  On the other hand, the particular problem that I'm
  referring to in this thread is the one where we were
  finding certain lower-case "u" characters in our
  particular TrueType font drawn halfway below the
  baseline. Based on your comment (Thanks!), I'll
  grab the latest Qt and see if that problem has been
  corrected; that fix would allow us to investigate
  using much-newer Qt versions.

                         Atlant

-----Original Message-----
From: qt-interest-bounces+aschmidt=dekaresearch.com at qt.nokia.com [mailto:qt-interest-bounces+aschmidt=dekaresearch.com at qt.nokia.com] On Behalf Of Konrad Rosenbaum
Sent: Sunday, June 12, 2011 09:21
To: qt-interest at qt.nokia.com
Subject: Re: [Qt-interest] Problems with Valgrind and Qt / QWS (*NOT* memory "leaks")

On Friday 10 June 2011, Atlant Schmidt wrote:
> * We'd be using a newer version of Qt but when 4.6.3 came out, we
>   encountered a font problem that prevented us from moving to that
>   version and so for the moment, we've "locked in" at 4.6.2.

The font rendering problems were solved in one of the early 4.7's.


        Konrad

This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.