is there any way to translate a xmind file into c++ code?
i mean state machine
write state machine code is painful
The opposite is also possible, output the StateMachine from C++ code (python, clang & graphviz)
@AlexisTM
@dotkt With HFSM2, making the machine is not that painful ;)
<3
The opposite is also possible, output the StateMachine from C++ code (python, clang & graphviz)
Yes. Several people already suggested I wrote a code generator / editor for HFSM2.
That would require a dedicated effort, which is not something I can afford with a full-time job :)
Also, supporting that tool would be an on-going commitment.
That said, if anyone wanted to take on such project - I'd support them (with advice / guidance) to the best of my ability.
BTW, I'm working on transition payloads. The API is likely going to look like this:
and
for all existing transition methods (
FSM::Instance::changeWith<TState>(const TPayload& payload)and
FSM::Instance::changeWith(const StateID stateId, const TPayload& payload)for all existing transition methods (
resume(), restart(), utilize(), randomize() and schedule())
At the moment I'm having trouble compiling in Microsoft Visual Studio 2019 16.6.5 (Windows 10 x64).
In fact, the example in https://doc.hfsm.dev/quick-tutorial does not compile for me.
I'll create an issue on that for clarity.
I'll need to allocate more time to building https://docs.hfsm.dev
Hello. I'm trying to integrate HFSM2 into my code and I'm running into a problem. I can't get the Context from a Control, only a FullControl. The docs say I should be able to, but it creates this error:
the object has type qualifiers that are not compatible with the member function
Hi @tastesliketriangle please open an issue https://github.com/andrew-gresyk/HFSM2/issues/new with a minimal code sample so I can verify on my end
Thanks, @DJuego !
Focusing on bringing https://gitter.im/andrew-gresyk/FFSM2 to close feature parity with HFSM2
Currently, only serialization and state access remain to be done
Focusing on bringing https://gitter.im/andrew-gresyk/FFSM2 to close feature parity with HFSM2
Currently, only serialization and state access remain to be done
The recent updates to HFSM2 were mostly formatting and minor tweaks with very minimal functional changes
At this point the highest priority work is around a multiplayer UE4-based demo and docs
At this point the highest priority work is around a multiplayer UE4-based demo and docs
That said, the previous logo didn't displease me per se.
It's true that the new logo seems more friendly to me. Why yellow and blue?
However this project probably doesn't have such a large community for that.
Whatever your soul decides will be fine, for that you are the supreme author.
In my case I have a weakness for symbolic logos. I would probably recreate myself in the recognizable/familiar scheme of a finite-state machine such as:
I would try in the HFSM2 logo to refer to its "hierarchy" or "regions" nature and in the FFSM2 logo to its "flat" nature.
so I've got a bit of a basic question. I want to have the fsm Instance as a member variable in my class, but every way I've tried to organize that has failed. part of the issue is that Instance doesn't accept a forward declaration of a state, it needs the full the from the cpp file. I guess I'm just wondering if there's an obvious way I'm missing or if there's another way I should be organizing my code?
e.g. if you're in UE4, and have an
AMyActor- I'd create a MyActor namespace and put all of the FSM code into it
Then I prefer letting
FSM being more of a 'brain' for the actor
AMyActor do all the heavy work, exposed via public API, and have the FSM call actor's functionsFSM being more of a 'brain' for the actor