Oops you're right, it's there. Thanks :) Simon
Opprinnelig melding Fra: Alan Alpert Sendt: 23:32 onsdag 30. april 2014 Til: Hausmann Simon Kopi: Hartmann Thomas; [email protected] Emne: Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future] On Wed, Apr 30, 2014 at 6:33 AM, Simon Hausmann <[email protected]> wrote: > On Wednesday 30. April 2014 15.25.35 Hartmann Thomas wrote: >> Hi, >> >> the original idea was to get rid of the need to write Java Script to change >> a state (state = "newState") and find a declarative way to change states. >> The rest then came naturally. > > Right. > > While we're on the state property: It's publically accessible through > setProperty/property. Does anyone know a reason as to why the setState/state > setters/getters aren't public API in QQuickItem itself? (but > Q_PRIVATE_PROPERTY) The QString state property and setState/state setters/getters are public API in my checkout of QQuickItem (release branch). -- Alan Alpert _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
