Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.6.0
-
None
-
6ab362a7e (dev), 8055247fc (6.6), 9ac3eab05 (6.6.0)
Description
There was a last minute suggestion on how the feature tags in the new QFont could be made a bit more type safe: https://codereview.qt-project.org/c/qt/qtbase/+/481748/comment/0475c6df_d2c47294/
If there is time before RC, we could push this through, we could potentially mark it as preliminary for now until a decision is made, or we could just use the current API, which should be fine in practice.
Tracking this with a blocking bug report instead of a comment thread in the API review, in order to proceed with the release process for now.
Attachments
Issue Links
- relates to
-
QTBUG-119899 make QFont mergeable by adding every kind of property to the (OpenType) "features"
-
- Reported
-
- resulted in
-
QTBUG-117046 Finalize feature API in QFont
-
- Closed
-
| For Gerrit Dashboard: QTBUG-116929 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 503279,2 | Mark feature API in QFont as preliminary | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 503683,3 | Mark feature API in QFont as preliminary | 6.6 | qt/qtbase | Status: MERGED | +2 | 0 |
| 503854,2 | Mark feature API in QFont as preliminary | 6.6.0 | qt/qtbase | Status: MERGED | +2 | 0 |