--- layout: "@layouts/ConfigLayout.astro" title: "Positioning" --- import MD_Title from "@components/MD_Title.tsx" # {frontmatter.title} QtQuick has multiple ways to position components. This page has instructions for where and how to use them. ## Anchors Anchors can be used to position components relative to another neighboring component. It is faster than [manual positioning](#manual-positioning) and covers a lot of simple use cases. The [Qt Documentation: Positioning with Anchors](https://doc.qt.io/qt-6/qtquick-positioning-anchors.html) page has comprehensive documentation of anchors. ## Layouts Layouts are useful when you have many components that need to be positioned relative to eachother such as a list. The [Qt Documentation: Layouts Overview](https://doc.qt.io/qt-6/qtquicklayouts-overview.html) page has good documentation of the basic layout types and how to use them. > [!note/Note:] > Layouts by default have a nonzero spacing. ## Manual Positioning If layouts and anchors can't easily fulfill your usecase, you can also manually position and size components by setting their @@QtQuick.Item.x, @@QtQuick.Item.y, @@QtQuick.Item.width and @@QtQuick.Item.height properties, which are relative to the parent component. This example puts a 100x100px blue rectangle at x=20,y=40 in the parent item. Ensure the size of the parent is large enough for its content or positioning based on them will break. ```qml @@QtQuick.Item { // make sure the component is large enough to fit its children implicitWidth: childrenRect.width implicitHeight: childrenRect.height @@QtQuick.Rectangle { color: "blue" x: 20 y: 40 width: 100 height: 100 } } ``` ## Notes ### Component Size The @@QtQuick.Item.implicitHeight and @@QtQuick.Item.implicitWidth properties control the _base size_ of a component, before layouts are applied. These properties are _not_ the same as @@QtQuick.Item.height and @@QtQuick.Item.width which are the final size of the component. You should nearly always use the implicit size properties when creating a component, however using the normal width and height properties is fine if you know an item will never go in a layout. This example component puts a colored rectangle behind some text, and will act the same way in a layout as the text by itself. ```qml {filename="TextWithBkgColor.qml"} @@QtQuick.Rectangle { implicitWidth: text.implicitWidth implicitHeight: text.implicitHeight @@QtQuick.Text { id: text text: "hello!" } } ``` If you want to size your component based on multiple others or use any other math you can. ```qml {filename="PaddedTexts.qml"} @@QtQuick.Item { // width of both texts plus 5 implicitWidth: text1.implicitWidth + text2.implicitWidth + 5 // max height of both texts plus 5 implicitHeight: Math.min(text1.implicitHeight, text2.implicitHeight) + 5 @@QtQuick.Text { id: text1 text: "text1" } @@QtQuick.Text { id: text2 anchors.left: text1.left text: "text2" } } ``` ### Coordinate space You should always position or size components relative to the closest possible parent. Often this is just the @@QtQuick.Item.parent property. Refrain from using things like the size of your screen to size a component, as this will break as soon as anything up the component hierarchy changes, such as adding padding to a bar.