NodeIndicator was trying to access properties from the Material attached
object. However, that one was shadowed by the Material type from
Quick3D. Avoid this by importing Controls into a namespace for
disambiguation purposes.
Also avoid a warning about mismatched types by explicitly casting
"parent" to a View3D before assigning it to a property of that type.
Pick-to: 6.10
Task-number: QTBUG-138176
Task-number: QTBUG-138177
Change-Id: I336455a3fdc9da610fc0e703328aec26bf3741f9
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
We can avoid confusion in qmllint by explicitly specifying that the
content module depends on RobotArm (using the target based dependency
API).
At runtime this happens to work because the application rearranges the
modules in the import path, but that's a runtime setting.
Pick-to: 6.10
Task-number: QTBUG-138176
Change-Id: I91e1a4142a691d70784380ef0de42fc198eaa3f7
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Both robotarm, and todolist examples were creating `content` target
which was breaking the build if both examples were activated.
Pick-to: 6.6
Change-Id: I0922765526f2fca861c16b1ced4f1c040c104adc
Reviewed-by: Jonas Karlsson <jonas.karlsson@qt.io>
Fabian Kosmale
Amir Masoud Abdol
Kimmo Leppälä