[Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

[Alan Alpert]

On Wed, Apr 30, 2014 at 6:33 AM, Simon Hausmann
<simon.hausmann at digia.com> 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