| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Reviewed-by: Trust Me
(cherry picked from commit 774a3536b00c4d6e4c4c10b708e31b4373a338e3)
|
| |
|
|
|
|
|
|
|
|
|
| |
Font names enumerated by Core Text cannot be found by
ATSFontFamilyFindFromName because ATS is expecting native names
instead of the names returned by Core Text. This patch get rid
of ATS font matching code in Cocoa code path to simplify the code,
avoid deprecation warnings (in the future) and fix this issue.
Task-number: QTBUG-11145
Reviewed-by: Eskil
|
| |
|
|
|
|
|
|
|
| |
RTL text would be positioned wrong with QGlyphs, as we would not
correctly detect the direction of the text and pass it into
getGlyphPositions(). The bidi analysis is the same as in the
QTextLine::draw() method.
Reviewed-by: Kim
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In order to support text decorations (overline, underline and strikeout)
in QPainter::drawGlyphs(), we need to call drawTextItemDecoration()
from this function. To support this, it has been generalized to no
longer require a QTextItemInt. We also need to propagate the decoration
attributes of the font from QTextLayout to QGlyphs, since this is not
part of the QFontEngine.
Task-number: QTBUG-12122
Reviewed-by: Kim
|
| |
|
|
| |
Mistakenly added in 171ad741fda84384a64ce56c847de7667051914c.
|
| |
|
|
|
| |
Hangul not supported on XP by default, so change the script in the
tests to greek instead.
|
| |
|
|
|
|
|
|
|
|
| |
Drawing to QImage will always go through the raster engine, so some
bugs might not be caught. This also fixes a test failure on X11,
since the raster engine on X11 is inconsistent with regards to
how it handles subpixel antialiasing into images. See task
QTBUG-11268.
Reviewed-by: Olivier
|
| |
|
|
| |
Static function which was never called, caused a warning with gcc
|
| |
|
|
|
|
| |
Also make the test find the font in shadow build
Reviewed-by: eskil
|
|
|
Introduce an API to access glyph indexes in a font directly.
A bug was discovered during this work, where different hinting flags
in loadGlyph() and loadGlyphMetrics() would make the metrics in
the two functions different, thus causing drawCachedGlyphs()
(which uses loadGlyphMetrics() indirectly) to use different metrics
than the standard drawTextItem() code path (which uses loadGlyph()).
The bug was visible in the tst_QGlyphs::drawExistingGlyphs() test.
Reviewed-by: Simon Hausmann
|
