hbpvis/zerobuf

zero-copy, zero-serialize, zero-hassle protocol buffers

zerobuf's Issues

Problem with ZeroBuff and [string] type

I'm Cristian Rodriguez, from the group working back in URJC/UPM with Pablo Toharia. Right now I'm trying to use a custom ZeroBuff fbs file that required a std::vector of char* (or vector) but zerobufCxx generates a std::vector when I use string or [string].
My fbs file contains:

namespace zeroeq.gmrv;

table SelectionStr
{
 ids:[string];
}

I've seen in the python script (zerobufCxx) it converts string to zerobuf::Vector< char >.
With the following fbs, I get the same result in the two attributes:

namespace zeroeq.gmrv;

table SelectionStr
{
 fooStrArr:[string];
 fooStr:string;
}

I had been trying to modify your Python script to generate std::vector (string) and std::vector<char*> ([string]), but I prefer to ask you how can I resolve this without change the script.
Any ideas on this?
Thank you!

Add support for arrays of dynamics zerobufs

The python fbs generator stumbles upon this:

table DataSource {
  url: string;
}

table Scene {
  data_sources: [DataSource];
}

>>> Dynamic arrays of empty ZeroBuf (field data_sources) not supported

Probably the allocator and the C++ side of things is not ready yet either, but hopefully @eile knows more about this.

Qt updated property signaling

• one property in the object called 'update' to signal if the buffer was updated (on ZeroEQ receive for instance)
• emit signals for changed properties after update: compare the buffer contents respectively (code generated) only for those properties