On Thu, 13 Feb 2014 00:19:42 +0100
Thomas Perl wrote:
> On 2014-02-12 20:36, Chris Walker wrote:
> > In the past (Harmattan code), I would have done this sort of
> > stuff :-
> >
> > onStatusChanged: {
> > if (status==PageStatus.Activating) {
> >
> > but there is no 'onStatusChanged' opt
On Thu, 13 Feb 2014 01:39:31 +0600
Andrey Kozhevnikov wrote:
> it's still there and working. no idea what wrong with your setup
Problem identified as being between the keyboard and the chair ;-)
Despite checking, I failed to spot that I was trying to insert the code
in the wrong place on the pa
Hi CDW
I also use onStatusChanged with no problems.
Is it possible that the event is being called earlier than you expect?
(e.g. during app startup?)
I would put a console.log in the onStatusChanged handler - outside the if:
onStatusChanged: {
console.log("Page XXX: onStatusChanged: statu
On 2014-02-12 20:36, Chris Walker wrote:
In the past (Harmattan code), I would have done this sort of stuff :-
onStatusChanged: {
if (status==PageStatus.Activating) {
but there is no 'onStatusChanged' option now. So what do I use now?
I've looked here -
https://sailfishos.org/sailfish
it's still there and working. no idea what wrong with your setup
On 13.02.2014 01:36, Chris Walker wrote:
In the past (Harmattan code), I would have done this sort of stuff :-
onStatusChanged: {
if (status==PageStatus.Activating) {
but there is no 'onStatusChanged' option now. So what
In the past (Harmattan code), I would have done this sort of stuff :-
onStatusChanged: {
if (status==PageStatus.Activating) {
but there is no 'onStatusChanged' option now. So what do I use now?
I've looked here -
https://sailfishos.org/sailfish-silica/qml-sailfishsilica-page.html but
it
