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

qmltypes format needs to make "foreign" explicit

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • P1: Critical
    • 6.8
    • None
    • QML: Tooling
    • None

    Description

      Currently, if you pull a foreign type into a module using QML_FOREIGN, its type description is copied into the current module's qmltypes. If you do that twice, you get two copies of the same type. It is often necessary to have two different QML types for the same C++ type, for example to expose a value type and its enums. However, expressing this as two copies of the same type, only differing in access semantics and exports is clumsy and creates problems for downstream tooling that expects internal names to be unique. Therefore, QML_FOREIGN and friends should work like QML_ATTACHED or QML_EXTENDED and link, rather than copy, the types.

       

       

       

      Attachments

        Issue Links

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

          Activity

            People

              qtqmlteam Qt Qml Team User
              ulherman Ulf Hermann
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes