Initial Choice State as Nested State of Data State

[BeAddicted]

Initial Choice State as Nested State of Data State

[nsk90]

Hi!
The quick reply is:
Here is a code which moves the data from DataEvent to a DataState
https://github.com/KStateMachine/kstatemachine/blob/master/kstatemachine/src/commonMain/kotlin/ru/nsk/kstatemachine/state/DefaultDataState.kt#L32
It is triggered in a moment of DataState activation.
In a sample that you have provided, the DataState contains initialChoiceState. This means that DataState is never activated. The ChoiceState is calculated before state activation, and the StateMachine goes directly to resulting state.
Imagine there are many ChoiceState redirections one by one. The library calculates resulting state path passing through all of ChoiceStates and activates states only on the last resulting destination (path). All intermediate state paths that were calculated during redirections are not activated. So it looks that you cannot access data from DateState in such case and butter to look directly into Event property.

The long reply:
I have to check this in runtime, this will take a while)

[nsk90]

But even if I do another problem occures. I then get the following exception:
java.lang.IllegalStateException: Last data is not available yet in MyDataState($38827186), and default data not provided.

I can not say why this happens, the code sample is provided for another case. You can provide another sample for this case, so I can see where the data is read from the DataState. Maybe If you read the data from Event there is no need to read it from the DataState? (and even use DataState api)

[BeAddicted]

Based in your first explanation I think the second problem seems to correlate. Both problems say that the data is not set even tough the state should be active. In the first case I activly try to get the data and run into an exception. In the second the statemachone itself seems to detect that there ist no data when transition into the state.

The code sample for this is pretty similar.

object MyDataState : DefaultDataState<Data>

addState(MyDataState) {
    initialChoiceState {
        if(true) {
             State1   
        }
        else {
             State2
        }
    }
}

Just dont use the Data in the code sample and make something like this (Code makes no sense but should trigger the problem, not at home to test this but pretty sure that was it).
I belive what happens ist that the state ist still triggered after the choice state but without the data event? Not really sure about that.