Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-117891

[REG 6.5.2 → 6.5.3] Unable to determine callable overload with QVariantMap

    XMLWordPrintable

Details

    • 8c2ea501f (dev), a8ab23b67 (6.6), dd7a8758d (6.5), 1f19f6f10 (tqtc/lts-6.2)

    Description

      The attached example runs into

      qrc:/breakitbaby/Main.qml:12: Error: Unable to determine callable overload.  Candidates are:

      It works if the signature contains i.e. int instead of a QVariantMap. It works if you don't wrap FooBase, but FooImpl for qml.

      Although the title is similar, it doesn't seem to be related to QTBUG-117675.

      Attachments

        1. breakitbaby.tgz
          1 kB
          Cajus Pollmeier

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-118556 assert failure when qml singleton calling inherited method from base cpp class

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-117805 Invocation of a C++ static method via an inherited QML singleton causes a crash

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-117852 [REG 6.5.2 -> 6.5.3] Qml crashes when singletons send signals

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-117959 Error: Unable to determine callable overload (calling slot in subclass)

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-118471 Js engine crash when calling signal of a singleton

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-117675 [REG 6.5.2 → 6.5.3] Unable to determine callable overload

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-117805 Invocation of a C++ static method via an inherited QML singleton causes a crash

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          mentioned in

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              fabiankosmale Fabian Kosmale
              cajus Cajus Pollmeier
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes