PropertyAction limitations should be documented better

I am using a SequentialAnimation which has a group of PropertyActions. First PropertyAction sets a text to Text component and the next PropertyAction changes the Text component's 'x' value based on the text length that was set in the first PropertyAction. This does not seem to work as the second PropertyAction sees the text length as 0. If this behavior is a limitation in PropertyAction or SequentialAnimation, it should be mentioned in the documentations.

Using a ScriptAction however works just fine and it can be used to achieve the exact same result.

I have attached an example project to demonstrate this issue.