previously on VL: VL Midsummer Night's Dream
here is to inform you of recent updates in VL land. We're still in feature-mode as we have a few things that we need in the first release even though they are quite advanced and a typical VL user will hardly come across them. Still, we figure, a few of you will be interested in:
The avid reader of this blog and tester already knows that a stateful patch (aka data type) in VL can be used in two different ways:
The process explorer is supporting the first of those cases in that it allows you to define the order in which operations will be called for a Process node. The simplest example of where this is interesting is when you patch a node like the FlipFlop which has a Set and a Reset operation. For the case where in one frame both of them are called it is important to specify which of them takes precedence. This is what you can now do in the process explorer by simply specifying the order of the individual operations. In addition it allows you to specify for some operations to not take part in the process at all by unchecking their indicator and to show (or not) a State output pin on the node...
Again: this is a rather advanced topic which the casual vl user will hardly ever come across. Still having this feature improves the pro-users lives and specifically the vl core library of nodes makes of course heavy use of that feature.
All this and more availble now in latest alphas.
Same as in the previous blog-post apply + we're hoping to reach a feature-freeze soon. We basically have one bigger rework to go that is supposed to make everyones lifes easier. In short: right now in VL when you create a new patch you need to decide beforehand between making an Operation, a Class or a Record. Those are all new concepts that are not so simple to explain to someone without any programming background. That is why we're now working on a workflow where this is not the first thing someone has to understand...nuff words, you'll see when it is done..
If you want to get started right now, here is what you do:
If you want to let us know that you like anything you just read...we're always up for a comment or even a flattr:
Nice, thanks for the report!
What is the "Show State Output" for?
I haven't asked this for a long time but seeing that you guys are working on UI enhancements I think it's justified to ask again: so when you freeze core features and done that bigger rework can we finally have if not the automatic library importer but a .net api for vl? Or even better the almighty standalone version?
@sebl: this is not interesting for typical process nodes like a FlipFlop or MonoFlop. but think of a more complex case, like a processnode wrapping a device (eg. leap, kinect,..). in such cases you'll want to be able to hand out the state of the node for downstream nodes to get.. (or even set..) on that state. hope that make sense...
@microdee: we know that many people are waiting for this and we're not happy about our delays here. the thing is that we're hoping to be able to present a clear and simple overview of how to create libraries for vl instead of throwing a bunch of code at people and let them figure out themselves and by that produce a series of confused questions for us to answer. we're at it, it has top priority (like so many other things) and we can only ask you to give us some more time. updates will certainly follow.
anonymous user login