Release catchup#8
Conversation
- Link to bluetheme - Detail `stable` procedures, and remove `beta` branch references
a220780 to
7943eda
Compare
4e7398b to
5c71a27
Compare
65ab35e to
fc1ec38
Compare
fc1ec38 to
14ff923
Compare
dbea2b1 to
365f2b5
Compare
47a2369 to
4c46402
Compare
5932600 to
bbba68e
Compare
rafaellehmkuhl
left a comment
There was a problem hiding this comment.
I made some comments about things I think can improved, but I'm approving already because this is already ULTRA good and should be shared with the world.
Great work Eliot!
| - Normally a sidebar tab arrow on the left | ||
| - Can be configured as a burger menu in the top left corner | ||
|
|
||
| ### Header Bar |
There was a problem hiding this comment.
It would be interesting to mention that both bars can be configured to be hidden and/or toggled with a Cockpit Action.
There was a problem hiding this comment.
I just tried that action and couldn't get it to work for the top bar - the bottom bar one works fine though.
| While other widgets generally have predefined behaviour, these are specifically designed to trigger and | ||
| set variables for use as parameters in [Custom HTTP Actions](#custom-actions). |
There was a problem hiding this comment.
They actually set variables in the data-lake, and so can be used in any Actions (or other places like external widgets, DIY widgets, etc).
| If the browser tab is changed away from Cockpit, or the Cockpit application window is minimised, | ||
| Cockpit loses access to the joystick inputs, and normally stops sending `MANUAL_CONTROL` messages | ||
| to reflect the loss of input. This can trigger an autopilot failsafe, which may not be desirable, | ||
| so an option is provided in the top right of the joystick page to tell Cockpit to repeatedly send | ||
| the last joystick input it received before losing access to the joystick. | ||
| > |
There was a problem hiding this comment.
It would be interesting to mention that one can avoid this kind of problem by having only the Cockpit tab in a given window and opening other tabs in another browser window.
It can also be avoided by using the self-contained version and not minimizing it (can be out of focus without a problem).
There was a problem hiding this comment.
Those are somewhat implied as-is, and seem out of scope of that warning to include specific details of.
| - `mavlink_disarm` | ||
|
|
||
| #### Custom Actions | ||
| It is also possible to define (and export or import) your own custom Actions, with a few different approaches: |
There was a problem hiding this comment.
It would be interesting to mention where the data-lake variables can be used on those actions (anywhere in a javascript action, on the parameters and body of a http action or in the message of a mavlink action).
5b72272 to
15b84ba
Compare
15b84ba to
def0bef
Compare
🔎 PREVIEW 🔍
Documents:
MANUAL_CONTROLcommands when there's no pilot input cockpit#713MANUAL_CONTROLmessages without vehicle cockpit#943USBconnections as valid tethered and automatically assign them cockpit#1061Minimally documents:
sentry.iocockpit#1166