-
-
Notifications
You must be signed in to change notification settings - Fork 264
Custom Buttons
Unlike Crankshaft Classic, Crankshaft NG supports custom buttons within it's tiled design.
Buttons are made by creating a config file in the /boot/crankshaft/
folder, one at a time, for each custom button.
The files must follow a button_1
, button_2
naming convention with a maximum of eight buttons available.
You can create the config files yourself or through the Crankshaft Management Tool, within a terminal:
crankshaft buttons 1
... for example, creates a config file for button 1 with default details, allowing you to then customize the button to your specific needs.
Each button file must include three values:
- Label (the text to appear on your button)
- Command (the command should to be executer when your button is pressed e.g.
/boot/crankshaft/custom/mycommand
) - Color code (the color for your button, as an RGB value - by default gray is assigned if not defined)
The #
character is used as a delimeter to separate values.
Example content of a custom button file, including a button colour:
Label#/path/to/my/command#255,255,255#
Example content of a custom button file, without defining a button colour:
Label#/path/to/my/command##
- Button pairs 1 & 2, 3 & 4 and 5 & 6 each share cells
- If only one button is defined within a cell, that button will expand to fill the whole cell
- Button 7 is shared with RPi cam (if enabled)
- Button 8 is shared with debug (if enabled)
- Empty cells are filled with a dummy button to complete the layout
- Home
- Roadmap
- General Changes / Changelog
- Installing / Updating
- When Issue occur
- Hardware
- Configuration
- Features
- Home
- Get started
- Hardware
- Software and Settings
- For Advanced Users
- Et Cetera