At the moment, I’m not able to get any member operations of a VL patch into vvvv. The only thing showing up is a patch with the pins of the Update operation. Is there any solid reason for that?
I got a datatype that does nothing but wrapping multiple fields of data. I have to manually create setters and getters for each field, which is annoying enough (but only for now, I get that). Not to get these getters and setters into vvvv, I have to create an operation in the document canvas for each one of those, which seems like a huge unnecessary overhead.
Also what was very confusing for me: if there is no update operation in a type, or it has no inputs/outputs, I get that node without inputs and outputs without explanation in vvvv.
All in all: the bridge between vvvv and vl, what shows up and what doesn’t, is 1) confusing and 2) unnecessarily restrictive.
Maybe I’m seeing it wrong though, I’d be happy to hear a better solution than creating an operation in the document canvas for each node I want to have in vvvv!
I do not really understand your last sentence - a box to tick what??
The reason that you can only expose the Update operation and nothing else is that from a vvvv perspective there’s only one entry point (Evaluate) therefor allowing only one defined operation to get called seemed reasonable. Allowing more would add unnecessary complexity to the hosting layer - things which all can be solved in the one Update operation wrapping your VL code.
I get that the bridge between vvvv and VL is rather tricky as soon as you come from a different route than cloning a well prepared template. We’ll definitely try to improve that over time (auto join/split, allow Patch/Class, red links in vvvv if pins get deleted etc.). In the meantime I encourage you to open a TTY in vvvv should you run into similar issues again - the hosting layer does spit out some error messages.
It’s basically got a few properties and readers / writers for these.
I understand that these readers and writers may at some point become automated so I don’t have to create them manually anymore.
Now I want to use this datatype inside vvvv, not as one node, but as something to pass around, read and write properties. I now have to go inside the document canvas and remake all those readers and writers, because I cannot expose them directly to vvvv - that was my main concern.
or in such a case (and don’t discard this thought too quickly): consider doing more parts of your project directly in vl and really only move to vvvv for drawing. can you name your particular reasons for wanting/needing to go via vvvv?
@Elias thanks a lot, good to know it’s just an out of date screenshot.
I guess that means for now my patch has to stay bulky as it is (for now)
I’m really looking forward to auto set/get, in any case!
@joreg i did have the same thought, just as I was reading through this again.
It might not be possible in my case for an untypical reason though: I want to use the patch for teaching newbies and want an easy to use ‘API’ that is in vvvv only, not split up into rendering vvvv and all else VL.
I’ll look into it again though.