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

[REG 5.13 ->5.14]Compiling with Qt 5.14 gives: "Unable to assign QJSValue to QVector<QPointF>" , was not in Qt 5.13

    XMLWordPrintable

Details

    • Linux/X11
    • ecdb4ed275a0869dc668d73d774735575d43a0a3 (qt/qtdeclarative/5.14)

    Description

      After updating the Qt version from Qt 5.13.0 to Qt 5.14 I started to get this printout
       
      file:///home/plover/test_workspace/testQt5.14/main.qml:12:9: Unable to assign QJSValue to QVector<QPointF>
      And sure enough, the TestQuickItem is no longer displayed on screen.

      When compiling with Qt 5.13.0 this issue does not occur, and the TestQuickItem is displayed.

      Attached is a minimal example test-application I created, that shows this clearly.  Change the Qt5_DIR from 5.13 to 5.14 and the issue occurs.

       

       

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-82743 [REG 5.13 -> 5.14] Assigning to QSet<QByteArray> property no longer works (due to conversion to js list while reading)

          • 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-80609 [REG: 5.13 -> 5.14] QSequentialIterable crashes in 5.14

          • 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

          Activity

            People

              fabiankosmale Fabian Kosmale
              plover Lovisa Irpa
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: