Can't understand the logic behind NodeStatus update code

[ADetilie]

Hello!

I am trying to adapt one BT library (not BehahaviorTree.cpp) to be compatible with Groot.
To make this, I need to understand how to encode BT and Node statuses changes in the format Groot can read.

With BT format, everything is more or less strait-forward:

• BT.CPP packs behaviour tree in a byte array using generated flatbuffers code from the schema in fbs file and sends it to Groot via ZMQ.

But with Node Status changes, everything became more tricky:

• From what I've seen, BT.CPP and Groot don't use StatusChangeLog table in from flatbuffer's types. And instead of this Groot uses some complex logic and byte arithmetic to decode needed info.
  

  Groot/bt_editor/sidepanel_monitor.cpp

  Line 51 in fae3806

  const uint32_t header_size = flatbuffers::ReadScalar<uint32_t>( buffer );

My question:
Are there any solid reasons for not using flatbuffer and do some custom logic with manually encoding/decoding node status changes?

[facontidavide]

Perfect timing, I am about to merge a branch that fix this

[ADetilie]

Thank you for your answer!
When are you planning to introduce these changes to your repo?