DISTRHO
/
JUCE
mirror of https://github.com/DISTRHO/JUCE
1
0
Fork 0
Code Releases 1 Activity
The JUCE cross-platform C++ framework, with DISTRHO/KXStudio specific changes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7842 Commits
11 Branches
3.6GB
Tree: 3cd4a9d917
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '3cd4a9d917'
${ noResults }
JUCE/modules/juce_blocks_basics
jules c81c33404d BLOCKS: Added support for tri-state button controls in littlefoot 8 years ago
..
blocks BLOCKS: Added support for tri-state button controls in littlefoot 8 years ago
littlefoot Moved all "namespace juce" declarations from module headers to the individual .h and .cpp source files. This makes life a lot easier for Intellisense and other IDE autocompletion tools 8 years ago
protocol BLOCKS: Added support for tri-state button controls in littlefoot 8 years ago
topology Moved all "namespace juce" declarations from module headers to the individual .h and .cpp source files. This makes life a lot easier for Intellisense and other IDE autocompletion tools 8 years ago
visualisers Moved all "namespace juce" declarations from module headers to the individual .h and .cpp source files. This makes life a lot easier for Intellisense and other IDE autocompletion tools 8 years ago
README.txt Added BLOCKS module 9 years ago
juce_LittleFootFunctions.dox Doxygen: Add top-level LittleFoot functions group 8 years ago
juce_blocks_basics.cpp Moved all "namespace juce" declarations from module headers to the individual .h and .cpp source files. This makes life a lot easier for Intellisense and other IDE autocompletion tools 8 years ago
juce_blocks_basics.h Moved all "namespace juce" declarations from module headers to the individual .h and .cpp source files. This makes life a lot easier for Intellisense and other IDE autocompletion tools 8 years ago

README.txt 


This is a JUCE module which discovers any connected BLOCKS devices and provides low-level

access to their physical properties.



Its job is to provide:

- topology and status information about the list of connected devices

- callbacks for touch events, control button presses and rotary dial movements

- simple control over individual LEDs

- optional rule-based virtual device aggregation functionality