[Qt-interest] QStateMachine API and design?

[Mihail Naydenov]

Considering qml has native states support, what is the need to hide a state 
machine behind a bool property?
I am really asking, because I am learning still.

Why not write a custom QDeclarativeItem with already predefined list of states 
("application states" the OP needed)?
Then anyone can hook to item.state and app states switching is handled behind 
the scenes in item.
Isn't it possible?


Just the whole example feels like some workaround of something QML should excel 
in.
The fact that QML does not even see states does not feel right...

Thank You
MihailNaydenov


----- Original Message ----
> From: Sean Harmer <sean.harmer at maps-technology.com>
> To: qt-interest at trolltech.com
> Sent: Mon, November 8, 2010 6:46:45 PM
> Subject: Re: [Qt-interest] QStateMachine API and design?
> 
> On Monday 08 November 2010 16:42:59 Andre Somers wrote:
> > Op Ma, 8  november, 2010 5:22 pm, schreef Sean Harmer:
> > > OK I have now had a  chance to have a play around with exposing a C++
> > > state machine such  that it can be used to control a QML based GUI. I'll
> > > write it  up
> > > as an entry on http://developer.qt.nokia.com/wiki too but here  is a brief
> > > run
> > > down on how it works along with a  tarball of my source code as it stands
> > > now.
> > 
> > Great  post Sean! A very nice writeup, you should definately put it on the
> >  wiki.
> 
> Thanks André. I'm now starting to write it up but I want to do it  in more of a 
>
> tutorial form so it might take me a little while to complete  it. ;-)
> 
> All the  best,
> 
> Sean
> 
> _______________________________________________
> Qt-interest  mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>