Hi @Blutimauge and welcome. I think SwipeView may be the wrong component for your use case. I would suggest looking into Flickable or the derived forms ListView/GridView. They handle end bouncing and continuous flow much better, as in it's build in. IIRC

Just to sit and answer my own question (but also trying to contribute to the forum's knowledge!)... I figured out that if I set interactive: false in the SwipeView, then everything works correctly-- it's just that you can't use your mouse to swipe left and right, which, could be argued, wouldn't be correct behavior in a windows/pointer desktop approach anyway. I'm guessing that there is something odd that happens in SwipeView when another window is opened. We are planning on targeting a touchscreen/fullscreen version eventually, in which case setting interactive: true and switching the Window creation to Popups would be the right thing to do anyway. I'm leaving as unsolved for now, just because I'm curious if anyone has any other ideas.

@pra7 said in QML SwipeView is covering entire window: w That's cool. This solution you came up with is perfect.

@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 }

First a note that SwipeView and its base type Container have gained some new members in Qt Quick Controls 2.1 in the upcoming Qt 5.8. These will help with your tasks: SwipeView::interactive Container::incrementCurrentIndex() Container::decrementCurrentIndex() For the time being, you could add the following binding as a temporary workaround until you will be able to use the new public interactive property: Binding { property: "interactive" target: swipeView.contentItem value: swipeView.currentIndex !== indexOfWebEngineView }

@jpnurmi, thanks a lot, already found this property. But had limit in 300 seconds to reply. Seems like u are guru of QML :)