I'd like to open a welcome dialog at startup which can be disabled by a
user.
Page
{
id: mainPage
function openWelcomeDialog()
{
var component = Qt.createComponent(WelcomeDialog.qml)
var popup = component.createObject(mainPage)
popup.open()
}
do not use onCompleted in this case. use status == PageStatus.Active instead
16.07.2014 14:58, Marcin M. ?:
I'd like to open a welcome dialog at startup which can be disabled by
a user.
Page
{
id: mainPage
function openWelcomeDialog()
{
var component =
This way the dialog opens after closing the dialog. Worked it around by
Component.onCompleted:
{
while (status != PageStatus.Active) {}
openWelcomeDialog()
}
--
Marcin
2014-07-16 11:01 GMT+02:00 Andrey Kozhevnikov coderusin...@gmail.com:
do not use onCompleted
Take back what I said. The workaround doesn't work. :P
--
Marcin
2014-07-16 14:42 GMT+02:00 Marcin M. marmistrz...@gmail.com:
This way the dialog opens after closing the dialog. Worked it around by
Component.onCompleted:
{
while (status != PageStatus.Active) {}
In this case you'd better connect to pageStack.busyChanged :) and wait
while pageStack.busy
16.07.2014 18:42, Marcin M. ?:
This way the dialog opens after closing the dialog. Worked it around by
Component.onCompleted:
{
while (status != PageStatus.Active) {}
Hi Martin,
I had the same issue while dealing with a similar problem where start
page was showing BusyIndicator while the application is loading. What
I did is connected to Component.onCompleted in ApplicationWindow,
start the initialization procedure and replace the page after
initialization is
Sorry Marcin, misread the name :)
2014-07-16 18:55 GMT+06:00 Dmitriy Purgin dpur...@gmail.com:
Hi Martin,
I had the same issue while dealing with a similar problem where start
page was showing BusyIndicator while the application is loading. What
I did is connected to Component.onCompleted in
Hi, 'Page.status' is the correct property to watch for avoiding this problem.
Here is an example of what you could do:
import QtQuick 2.0
import Sailfish.Silica 1.0
ApplicationWindow {
initialPage: Component {
Page {
anchors.fill: parent
On Wed, Jul 16, 2014 at 11:25 PM, Matthew Vogt matthew.v...@jolla.com wrote:
Hi, 'Page.status' is the correct property to watch for avoiding this problem.
Here is an example of what you could do:
import QtQuick 2.0
import Sailfish.Silica 1.0
ApplicationWindow {
initialPage:
Yes, fair point.
IIRC, we decided there weren't enough motivating examples to make it worth
adding action-queueing behaviour to the PageStack. If people keep hitting this
problem, though, it could be worth revisiting.
That said, working around the problem is usually simple, and making the
10 matches
Mail list logo
