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. Should KeyNavigation.priority behavior depend on where it is in the QML?
QtWS25 Last Chance

Should KeyNavigation.priority behavior depend on where it is in the QML?

Scheduled Pinned Locked Moved QML and Qt Quick
1 Posts 1 Posters 558 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.
  • R Offline
    R Offline
    Rolias
    wrote on last edited by
    #1

    I'm just trying to figure out some things so I have two rectangles and you move between them with up arrow and down arrow. Works fine. I also have an onPressed handler that prints what key is pressed in the rectangle. If I add
    @KeyNavigation.priority: KeyNavigation.Before@

    and have that line before the Keys.onPressed handler then the navigation key moves between the rectangles and the key is not printed. If I move the KeyNavigation.priority after the onPressed handler then the key is printed. Is this how it's supposed to behave? I would have thought in a declarative language like QML this type of ordering wouldn't be relevant. I don't want to report a bug if this is working as designed.

    Check out my third course in the trilogy on Qt
    "Integrating Qt Quick with C++"
    http://bit.ly/qtquickcpp
    published by Pluralsight

    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