Eyetracking utilization

[smlpt]

Changes made by Ruoshan to implement a bridge for Mastodon tracking to Sciview, as well as utilize eye tracking in Sciview.

[kephale]

Just checking how you're doing on this @smlpt!

It looks pretty merge friendly, but I'm curious if there is anything else you need on the sciview side?

[smlpt]

Just checking how you're doing on this @smlpt!

It looks pretty merge friendly, but I'm curious if there is anything else you need on the sciview side?

I am currently in the process of refactoring many of the tracking classes, because they were all created as command style classes, making it tedious to call them from code (I couldn't really call any member function except for run()). So I'm going to extract their functionality into separate classes, and then the Demo-named classes simply exist for the command purpose (like I already did in 886997a for the EyeTracking class).
I also consolidated most of their functionality into a base class, because several different classes (EyeTrackingDemo, VRControllerTrackingDemo, VRHeadsetTrackingDemo, Test) all shared large chunks of more or less identical code.

So to answer your question: this branch turned into an active construction site again, and I may have to refine a few more things related to the tracking before we can merge it.
Or do you think its better to merge a basic (working) version of the branch first, and then keep working on it in a new branch?

I would also appreciate if this branch could be merged into scenery soon™, in case I need to add other stuff to scenery.

[smlpt]

This should now bring some order into the naming scheme.
NB: The CI is still failing because I am using the "centered" keyword when showing camera messages, and this feature isn't part of a new scenery release yet (but only exists in scenery main, which I include locally).
(Well and also the grid traversal volume sampling from the corresponding scenery branch)