I am trying again to get into the VL world. I have a nice use-case, where I want to create a VL library for receiving data form a LSL (LabStreamingLayer) servers. I am using this to fetch EEG LSL streams form a MUSE2016 EEG headband, send by the opensource BlueMuse.app.
I started all from scratch and gave up on generic VL lib, so I have created a class(Muse), where in the “Create” I scan for all the available streams (blocking for a few sec…, whatever) and then I set some pads
I plan to use the pads later to pull data async and process it (not there yet, unfortunately )
However…but as I look how it goes as of now for me with VL, perhaps I go for the plain old c# plugin + threads and the good old VVVV…
will give a try to VL again after some time… it is really frustrating
Are “pads” class properties (class variables with getters and setters?) then what are the input/outputs then?
This all is very confusing…
Is the “create” operation a constructor?
What about the update? Is it running based on the Main Loop (which mainloop? Now one can have many)!
It is strange, but I do not get the results from the AsyncTask …
this will create the Muse class in every frame, i’m not sure if that is what you want…
however, you seem to miss a few basics, especially how operations (methods) are used. and you can’t expect to learn a new programming language in 2 hours.
yes, they are class variables. this thread gives an easy example with code comparison:
the Update of the application patch (main patch of the document) gets called by the runtime main loop, if you place things into it, they will be called by the application patch… and so on… like a call hierarchy in most other programming languages.
it is a bang, you seem to have a toggle connected, which restarts the task in every frame.
which documentation did you read/watch so far and what is missing for you?