i have an another idea for you:
...
var newPage = pageStack.push(Qt.resolvedUrl("newPage.qml"), {...})
newPage.done.connect(thisPage.pageDone)
...
//thisPage
...
function pageDone(var1, var2, var3, ...) {
//do something with var
}
...
//newPage
...
signal done(string var1, int var2, string var3
Hi Chris
thanks for this idea and your code example!
I am working on app in a very early stage that will partially talk to a
remote server and get dynamic content. In some cases it even will create
a little bit of traffic...
...so I will stick for the moment with the solution provided by Kon
+1 for Dialog
Andrey Kozhevnikov schrieb am 17:32 Donnerstag, 5.Juni
2014:
why not to use Dialog instead of Page for this use case?
05.06.2014 21:28, Michael Neufing пишет:
Hi Chris,
>
>
>one problem I see with your solution is that the App could take long time to
>launch, when there a
why not to use Dialog instead of Page for this use case?
05.06.2014 21:28, Michael Neufing ?:
Hi Chris,
one problem I see with your solution is that the App could take long
time to launch, when there are a bunch of Pages that have to be
initialized at launch (depending on the structure of
Hi Chris,
one problem I see with your solution is that the App could take long time to
launch, when there are a bunch of Pages that have to be initialized at launch
(depending on the structure of the Pages).
So I would prefer lazy loading Pages, which will be initialized when it is
needed.
Hi Markus
In my app I chose to instantiate all my Pages in the same place. Each of
the pages has a declaration in a separate qml file (e.g. MainPage.qml,
AreaSelectionPage.qml).
With this architecture none of the declarations need to know about the
previous or next page. It is not their conc
Yes! Works perfect!
Thanks a lot!
Somebody dancing right here...
Markus
Am 05.06.2014 15:23, schrieb sfietkonstan...@free.fr:
Hello !
The previous page might not be available (actually components created
dynamically might not be aware of other dynamically created components, as it's
the ca
Hello !
The previous page might not be available (actually components created
dynamically might not be aware of other dynamically created components, as it's
the case with pages). You can communicate the page as a property to the new
page:
Page {
id: somepage
...
pageStack.push(Qt.
Thanks, but I am still stuck. This is what I do
PreviousPage.qml
Page {
id: previous
property string topic: "default value"
...
Topics.qml
Page {
id: topics
property string topic
...
Button {
id: topic0
text: qsTr("Topic 0")
you need to give the page id
Id: PreviousPage
2014-06-05 15:43 GMT+03:00 i...@flyingfischer.ch :
> Thanks for your inputs!
>
> Calling
>
> PreviousPage.topic = "MyTopic";
> pageStack.pop();
>
> gives me a ReferenceError: PreviousPage is not defined.
>
> PreviousPage.qml and property string topic
Thanks for your inputs!
Calling
PreviousPage.topic = "MyTopic";
pageStack.pop();
gives me a ReferenceError: PreviousPage is not defined.
PreviousPage.qml and property string topic do exist.
Thanks for your patience!
Markus
___
SailfishOS.org Devel
Sali Markus
I would also love to see a pop() method with parameters so I can pass info back
to the previous page, jus like the push()
As a workaround I just set the page's properties directly immediately before
the pop() call e.g:
AreaSelectionPage {
id: areaSelectionPage
if you using Dialog you can set dialog.acceptDestinationProperties =
{something: true}
05.06.2014 17:48, i...@flyingfischer.ch пишет:
Beginners follow up question
Hello
while transfering parameters works fine with
pageStack.push(Qt.resolvedUrl("nextPage.qml", {topic: "myTopic"}))
there seem
Beginners follow up question
Hello
while transfering parameters works fine with
pageStack.push(Qt.resolvedUrl("nextPage.qml", {topic: "myTopic"}))
there seems not to be any method like this in
pageStack.pop()
How can I give back a parameter from the top of the stack to the
previous page?
Autsch!
Thanks! Works like a charm!
;-)
Markus
Am 05.06.2014 10:07, schrieb Andrey Kozhevnikov:
onClicked: pageStack.push(Qt.resolvedUrl("nextPage.qml"), {topic:
"myTopic"})
second parameter should pass to push, not resolvedUrl function
05.06.2014 14:05, i...@flyingfischer.ch пишет:
onClic
onClicked: pageStack.push(Qt.resolvedUrl("nextPage.qml"), {topic:
"myTopic"})
second parameter should pass to push, not resolvedUrl function
05.06.2014 14:05, i...@flyingfischer.ch пишет:
onClicked: pageStack.push(Qt.resolvedUrl("nextPage.qml", {topic:
"myTopic"}))
_
Caution, truely a beginners question...
Hello
I am stuck on retrieving information from a previous page in the next
page. This is what I try to do:
Send a parameter to nextPage by
onClicked: pageStack.push(Qt.resolvedUrl("nextPage.qml", {topic:
"myTopic"}))
Try to retrieve the parameter o
17 matches
Mail list logo
