thanks for your feedback. Currently we are bound mostly by DevKitchen preparations. But we promise to get back to this issue and think about other options as soon as we find the time.
Until then: If you click on the "unread message queue", there in the top right you have commands to mark messages as read, either all or just for certain categories. Maybe this can at least ease your pain, until we find the time to address the issue.
Although I'm glad to hear that it actually didn't showed up again, there are actually backup activities running twice a week but they should not interfere at all with the normal board functionality. So far I'll take a look at it.
That said, if a similar situation will happen again in the future, please provide us with the precise time in order to help us browse and verify through the logs.
Hi! You could go for CTracks via Python. You'd have to get the track for a position parameter, for example, or create one, then get curve, then add keys. Later, you could simply range map it back to your Xpresso rig. it It's definitely doable!
For everybody interested in syntax highlighting, nodeBB is pretty smart in recognizing the language you're using by simply checking your code snippet, but in case you really want to hard-code the language set simply use the following line when starting a code snippet:
```<language>
where <language> can be anything like python or c++