Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. StackView Push Appears To Have A Bug..
Forum Updated to NodeBB v4.3 + New Features

StackView Push Appears To Have A Bug..

Scheduled Pinned Locked Moved Solved QML and Qt Quick
3 Posts 2 Posters 853 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PSI_lbc
    wrote on last edited by PSI_lbc
    #1

    When you do a stackview.push() the item being pushed never receives an onVisibleChanged signal. None of the controls on the "item" receive the onVisibleChanged signal either.

    When you do a stackview.pop() the item, and all the controls on the item, being popped do receive onVisibleChanged and visible is equal to false..as one would expect.

    So what am I missing?

    Is this the normal, expected operation of the stackview control?

    The push() just does the default stackview slide animation..nothing special.

    Are the onVisibleChanged signals being re-directed or eaten by something in QML on purpose? If so, what and how do I change that behavior?

    From my way of thinking (not always correct), it would seem appropriate to emit a onVisibleChanged signal when the stackview slide animation of some item has completed.

    P 1 Reply Last reply
    0
    • P PSI_lbc

      When you do a stackview.push() the item being pushed never receives an onVisibleChanged signal. None of the controls on the "item" receive the onVisibleChanged signal either.

      When you do a stackview.pop() the item, and all the controls on the item, being popped do receive onVisibleChanged and visible is equal to false..as one would expect.

      So what am I missing?

      Is this the normal, expected operation of the stackview control?

      The push() just does the default stackview slide animation..nothing special.

      Are the onVisibleChanged signals being re-directed or eaten by something in QML on purpose? If so, what and how do I change that behavior?

      From my way of thinking (not always correct), it would seem appropriate to emit a onVisibleChanged signal when the stackview slide animation of some item has completed.

      P Offline
      P Offline
      PSI_lbc
      wrote on last edited by
      #2

      @PSI_lbc

      OK..a little digging and reading of the docs (gosh that helps)..

      stackView.push( {item: Qt.resolvedUrl( url ), properties: { objectName: name, visible: false }} );

      If you pass the visible property as "false", at the end of the slide animation, visible is changed to "true" and the onVisibleChanged signal is emitted..as expected.

      You would think "visible: false" should be the default in the "properties" list..

      1 Reply Last reply
      0
      • GrecKoG Offline
        GrecKoG Offline
        GrecKo
        Qt Champions 2018
        wrote on last edited by
        #3

        Or you could use the StackView.status attached property.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved