Don't calculate the most fitting size, adopt a reasonable size and go with it.
BUG: 417454
Plasma |
Don't calculate the most fitting size, adopt a reasonable size and go with it.
BUG: 417454
Played around with it
No Linters Available |
No Unit Test Coverage |
Buildable 22400 | |
Build 22418: arc lint + arc unit |
FixedSize 25pt does help, but "2 glyph emojis" will overlap each other.
Rectangle { width: parent.contentWidth height: parent.contentHeight border.color: "#f00" anchors.centerIn: parent border.width: 1 color: "transparent" }
uh right, didn't see that. Actually, do you know what's up with those? we should just be showing them as 1 glyph...
Not sure. Backwards compatibility?
Firefox renders a couple of them fine, while the TaskManager widget doesn't. Could it be the "Noto" font? The facepalm ones not working are 3 glyphs merged together (facepalm+skincolor+sex). It's rendering (facepalm+skincolor) fine though.
There are some glyphs that don't render in firefox either. They don't have a Google (who works on Noto) emoji.
So we'll need to account for double glyphs.
No, it's not.
@Zren
Another thing we could do is taking such multiglyph renders as a bug on the font. We can clip them so they don't overlap each other. In the end, it's not like seeing them resized is pleasing to the eye either...
As in clip: true?
delegate: MouseArea { width: emojiView.cellWidth height: emojiView.cellHeight clip: true Rectangle { border.color: "#ff0"; anchors.fill: parent; border.width: 1; color: "transparent" } QQC2.Label { font.pointSize: -1 font.pixelSize: Math.floor(emojiView.desiredSize / 2) Rectangle { width: parent.contentWidth height: parent.contentHeight border.color: "#f00" anchors.centerIn: parent border.width: 1 color: "transparent" } } }