Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.12.1, 5.12.2
-
-
aa51b3bf4ea854ffe7b39403289689daa428b221 (qt/qtdeclarative/5.12) 28a114cbf7a3c2c18948e8bd582e5b5463443cab (qt/qtdeclarative/5.12)
Description
QML enums behave weird if the component containing the enum resides within some module and still {{import}}s that same module.
See the attached example.
If you make changes (adding whitespace and removing it again is sufficient) to the App.qml file and save it, the next Run of the application will result in the enum being undefined. Just pressing the Run button a second time fixes this and the enum is working as expected. Make a change in App.qml and save again to repeat the problem.
If you then remove the import Components 1.0 line from App.qml, it works fine.