gmabey

I've now resolved the functional issues I was working against the last time I pushed an update to my fork (nested messages). The following tests now work: `test_extra_namespace`, `test_protobuf`, `test...

@semlanik I'm sorry to hear you haven't been doing well and I hope that you recover soon. I just now pushed some more changes to my `shareddata` branch after finding...

P.S. One of the other ways (I think) to use the message contents in QML is to have the message as a property of another class that *does* inherit from...

P.P.S. I'd love it if there was a simpler way to handle the initialization of nested messages (it really hit hard in the cyclic loop scenario) than using `Q_GLOBAL_STATIC` but...

@semlanik any further thoughts on this suggestion? I need to go back and merge your recent commits into my branch, but haven't yet. I am still actively using and appreciating...

@semlanik in case it wasn't clear, one of the main snags I hit as I was trying to get the gRPC stuff to work was the use of `QPointer`, in...

@semlanik I'm working today on trying to get my fork to compile for Windows, but it's getting pretty ugly. I sure wish I was better at the `cmake` ninja techniques...

@semlanik Do you mean the whole qtprotobuf project? Or, just abandoned the idea of switching your repo to use Q_GADGET? I hope that you will reconsider someday. Particularly for the...

@arth7s3 on windows, I have found it useful to make sure that `protoc.exe` is on the PATH.

@Rightbputnow1 yes you're right -- I probably should have deleted my comment when I realized it didn't solve the problem, but at least I can confirm the behavior :-/