Skip to content
  • 144k Topics
    722k Posts
    S
    Hey Bob64, It sounds like you're on the right track with your idea to go for a simpler, ad hoc approach. Using two sibling items and toggling their visibility/opacity based on hover seems like a good, lightweight solution—especially if you're aiming for something less heavyweight than StackView. If you want to add a little extra polish, you could also experiment with Transitions and Behavior in QML to animate the opacity changes, giving it that smooth, Qt Creator-style feel. That way, you could achieve something closer to the hover-based description transition you want, without over-complicating the delegate structure. I think StackView might be overkill here, as you mentioned, especially since it’s designed for more complex page-level transitions. StackLayout doesn’t seem to give you what you need in terms of transition effects, so your ad hoc solution seems more practical for a simple case. Let me know if you need any more details or help setting up the hover logic. Best of luck! Image { id: exampleImage source: "example.jpg" anchors.fill: parent smooth: true } Text { id: descriptionText text: "This is an example description." color: "white" anchors.centerIn: parent opacity: 0 font.pixelSize: 16 wrapMode: Text.Wrap horizontalAlignment: Text.AlignHCenter } MouseArea { id: hoverArea anchors.fill: parent onClicked: { console.log("Item clicked!") } onHoveredChanged: { descriptionText.opacity = hoverArea.containsMouse ? 1 : 0 } } Behavior on descriptionText.opacity { NumberAnimation { duration: 300 easing.type: Easing.InOutQuad } }
  • Jobs, project showcases, announcements - anything that isn't directly development
    4k 23k
    4k Topics
    23k Posts
    DeSGuND
    @JonB read post more once and did through qml thanks an answer
  • Everything related to designing and design tools

    127 383
    127 Topics
    383 Posts
    R
    I see this is an old thread and I see several unresolved threads on this topic. I'm leaving this incase it helps someone else who ends up here. The solution was twofold for me. Go to File > Export Project and select Enable Python Generator. This will create a main.py. Make sure you pip install PySide6-DS Hope this helps someone.
  • Everything related to the QA Tools

    77 213
    77 Topics
    213 Posts
    J
    Hello i am using WinCC OA to develop a qt application. WinCC OA has some custom elements which cannot be detected by squish for example a polygon. Squish is now not able to detect this element with the picker. I know the name of the element but as it is of WinCC OA internal i do not know the type: waitForObject( {"container": "container", "name": "POLYGON1","type": "???","visible": 1} ); How do i get this information? And what to use if unknown? Is there any other way? I mainly just need to click this element. Thanks a lot
  • Everything related to learning Qt.

    382 2k
    382 Topics
    2k Posts
    P
    Hello everyone, I've been trying my hand on QT for a while now but with QT Academy I have now a path to follow to keep my motivation high. This is my solution for the first challenge of the QML for Beginners learning path. Github repository: https://github.com/PaulBroken/Intro_QML_challenge/ with some screen and video: https://github.com/PaulBroken/Intro_QML_challenge/tree/main/screens For the button showing info details I used the QtQuick States. I'm not familiar with States yet but I wanted to try something new (to me) that seemed suitable for this purpose. I still have a flickering problem when the windows is resized and the binding width/heigth to keep the card ratio seems not work when I change the windows width. So still a lot to learn but the trip is started! [image: c8124755-be16-4e05-a82e-d123e774b9d1.png] [image: 8d143321-7d46-426c-8ac7-477c791a7fab.png]
  • 2k Topics
    13k Posts
    SGaistS
    @swankster that's a job for either a proxy model or a QStyledItemDelegate.
  • 4k Topics
    18k Posts
    msauer751M
    @Pl45m4 Ja Hab ich. Dies ist die komplette Datei. #pragma once // Includes //--------------------------------------------------------------------------------------------------------------------- // own header // other includes // system includes #include <QtCore/qglobal.h> // Macros/Defines //---------------------------------------------------------------------------------------------------------------------- #if defined(LIBDB_LIBRARY) # define LIBDBSHARED_EXPORT Q_DECL_EXPORT #else # define LIBDBSHARED_EXPORT Q_DECL_IMPORT #endif // Forward declarations //----------------------------------------------------------------------------------------------------------------------
  • This is where all the posts related to the Qt web services go. Including severe sillyness.
    1k 10k
    1k Topics
    10k Posts
    SGaistS
    @RokeJulianLockhart to the best of my knowledge, no. The first release of Discourse was in 2014 and the forum is several years older than that.