A disappointed QML user (boy, am I happy that Digia is going to maintain and develop QtWidgets during the lifetime of Qt 5.x: http://blog.qt.nokia.com/2012/08/09/digia-extends-its-commitment-to-qt-with-plans-to-acquire-full-qt-software-technology-and-business-from-nokia/).

Row {

y:40
anchors.horizontalCenter: parent.horizontalCenter
spacing: 10

Repeater {
id: repeater
property int currentIndex: 4
model: ["/home", "/username", "/some", "/pseudo", "/path"]

Text {
text: modelData
font.pixelSize: index == repeater.currentIndex ? 40 : 20
color: “white”
anchors.baseline: parent.verticalCenter

}
}
}
}

import QtQuick 1.1

Rectangle {
width: 800
height: 100
color: “black”

Row {
anchors.horizontalCenter: parent.horizontalCenter
height: parent.height

Repeater {
id: repeater
property int currentIndex: 4
model: ["/home", "/username", "/some", "/pseudo", "/path"]

Text {
text: modelData
font.pointSize: index == repeater.currentIndex ? 40 : 20
color: “white”
anchors.baseline: parent.verticalCenter
}
}
}
}

Just posting the snippet for ease of use

Giving the row item a proper height then adding “anchors.baseline: parent.verticalCenter;” to the Text item gives me precisely what you want.

Look like a bug.

I know why that happens.Your printing the text in a loop meaning that each individual text is on it’s own.

If you where to print it like this:
Text {
id: name
text: “/home/username/some/pseudo/path”
color: “white”
}

then you do get the baseline you want. And yeah, then it gets a whole lot more complicated to do whatever you want to do since you can’t simply say “click path”.. How would you know where path is

What you can do – which will make it a whole lot more complicated – is making a custom “fontdata” object from http://qt-project.org/doc/qt-4.8/qfontmetrics.html. Yes, just to get/calculate the base line!

Another thing you can do is report a bug (or feature request) in Qt to request a baseline property in the Text component.

Good luck!

You do not need to do everything with QML base components as shipped with Qt 4.8. Just look if there are other components which may do what you like to achieve or use QDeclarativeItem/QGraphicsItem to write yur own component(s). That enables full access to QFontMetrics and all of Qt. You could also go with tge easy way to just export a qreal fontBaseline(QString, QFont) and do the offser calc/positioning in QML.