Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. Qt 6
  4. QTouchEvents::TouchPoint class migration from Qt5 to Qt6
Forum Updated to NodeBB v4.3 + New Features

QTouchEvents::TouchPoint class migration from Qt5 to Qt6

Scheduled Pinned Locked Moved Unsolved Qt 6
2 Posts 2 Posters 417 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.
  • H Offline
    H Offline
    Himanshu Rohilla
    wrote on last edited by Himanshu Rohilla
    #1

    Hello Everyone,

    We are migrating our legacy product source code from Qt5 to Qt6. While migration, we found that
    QTouchEvents::TouchPoint class earlier had various set APIs(Eg: setState, setPos,setNormalisedPos, setRect, setSceneRect, setScreenRect, etc) which are removed in Qt6 along with the class itself. After going through Qt6 documentation it is discovered that QTouchEvents::TouchPoint class has been replaced with QEventPoint class where we could explicitly set only selected parameters through constructor.

    As of now we are using QEventPoint class constructor with available parameters being set , going forward it would be great to know -

    1. The reason for those omission of set APIs
    2. Is there any alternate class or API implementation apart from QEventPoint for legacy QTouchEvents::TouchPoint set APIs.
    3. If there are no alternate apart from QEventPoint , then, is setting parameters through constructor enough and ignoring other setters?

    Thanks in advance.

    HImanshu Rohilla

    1 Reply Last reply
    0
    • VRoninV Offline
      VRoninV Offline
      VRonin
      wrote on last edited by
      #2

      I found the source of the change but there is not much more colour on the reasoning behind it. The setters were explicitly moved in the private API so constructors look like your only option (unless you want to use the private headers)

      "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
      ~Napoleon Bonaparte

      On a crusade to banish setIndexWidget() from the holy land of Qt

      1 Reply Last reply
      2

      • Login

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