savvasioHi Elliot, everyone. Not sure if this is the right place to ask so feel free to delete it if not. I would like to ask if there was a specific version of RULR for the workshop, one that is able to talk to the Astra cam. And if so can u share more please? Attended the workshop only as a viewer so I couldn't get the files. Tnx
Elliot WThere are multiple ways to work with sliders:
Put your cursor anywhere in teh active area of the slider (you will notice the graphics change slightly as you roll your mouse over), then begin dragging left or right to change the value. Note that the position of your cursor doesn't matter, only the movement. This helps with speed and accuracy.
Double click jump
Simply mouse over anywhere in the active area of the slider and double click to jump the value.
Hold to zoom
This is similar to dragging, but gives us more accuracy. Just hold the mouse still for at least a second before you start moving, and you'll notice it starts to zoom the values. The longer you hold, the more it zooms. This is good for delicate accuracy.
Enter value as text
Click the pencil icon, and a text box will appear allowing you to enter your value manually. If you leave the box empty or hit cancel then no change will be made.
is there a way to import the transform values generated by the dx11 pointcloud calibration into rulr and then do the kinect projector calibration? it would help a lot using the dx11 pointcloud blobextraction...
(Notice how the namespaces are mirrored in the filename paths)
Now try it!
Run Rulr, and check the node browser. Tada! you should find your node there.
Add it to your patch, and see it sit there doing nothing. Hooray!
Implementing node functionality
Events rather than overrides
Often when we make a new node, we want to copy in functionality from existing nodes into the new one. E.g. Cameras and Projectors have a lot in common, so they both inherit from the View node which describes the way cameras and projectors see the world.
Inheritance is great! But then we get stuck in patterns where the child class must be sensitive to whatever the parent class implements itself. E.g. if we were to override the drawWorld function, then we might accidentally disable the parent class' drawWorld function. We can then fix that by explicitly calling `Parent::drawWorld`, but we may forget to do that, or the parents functions might change without us knowing.
We deal with this problem in Rulr by using events rather than overrides. Each node has a set of events: