I went with the Binding solution in the end :)

@Steve-Fallows,

Just to clarify is receptorPath_textField also an id?

in that case your code

CTPanel { id: ct_panel Component.onCompleted: { ct_panel.setUp() // Complete set up of the C++ object console.log("CT Panel component completed.") } receptorPath: receptorPath_textField.text }

should work wherever it is placed (in the same qml file).

if receptorPath_textFieldis is a grouped property from CalibrationPageForm and the id of the page is page

Have tou tried?

CalibrationPageForm { id: page receptorPath_textField.text: settings.receptorPath } CTPanel { id: ct_panel Component.onCompleted: { ct_panel.setUp() // Complete set up of the C++ object console.log("CT Panel component completed.") } receptorPath: page.receptorPath_textField.text }

@jsulm Yes, i agree with you. But as per above requriment i gave that sample.

hi
"
When a signal is emitted, the slots connected to it are usually executed immediately, just like a normal function call. When this happens, the signals and slots mechanism is totally independent of any GUI event loop. Execution of the code following the emit statement will occur once all slots have returned. The situation is slightly different when using queued connections; in such a case, the code following the emit keyword will continue immediately, and the slots will be executed later."

http://doc.qt.io/qt-5.5/signalsandslots.html

Hi,

Just a quick note, if your widget on stack (i.e. leDimWidth) gets a parent, you'll have a double delete problem since it will get destroyed when the parent is and again when your Stacker object gets destroyed.

Good news! My use case is actually well covered by simply using a regular .import "thing.js" as Thing. I don't need the specific namespace-less behavior of Qt.include; I just happened to miss .import when reading the doc, thus failing to understand that Qt.include is only a second import mechanism to be used instead of .import under very specific (documented) circumstances.

→ Doc might still deserve clarification of the async behavior, but my initial problem is gone with using .import. I updated the QTBUG

@JKSH Thanks for your help, May you help me more by writing a sample code for this ?

Thanks