List number of devices (online and offline) at top of the device list.
Enumerate the devices in a column on the left (just makes it easier to count them, though this could be confusing with IDs as well).
Function that can copy the full list of IP addresses or hostnames to clipboard (useful for making your own notes, and running your own batch scripts).
Batch script for arbitrary sending of files to devices (specify anywhere in the file system to write).
There are cases where the main HBAction running thread gets stuck or crashes. Some way to reboot that thread (perhaps automatically on the reset message).
Ditto with the main OSC broadcast listener thread. Any others? Perhaps reset needs to completely rebuild the class?
Perhaps reset should NOT clear the store field. Not that this is really being used.
Implement a series of timestamped event routines, given that we have NTP working very nicely now. doAtTime(). Some basic maths for calculating future beat times. A standard protocol for sending tempo/beat schedules into the future (e.g., plan and share a list of beat, tempo and event-time tuples?).
List number of devices (online and offline) at top of the device list. Enumerate the devices in a column on the left (just makes it easier to count them, though this could be confusing with IDs as well). Function that can copy the full list of IP addresses or hostnames to clipboard (useful for making your own notes, and running your own batch scripts). Batch script for arbitrary sending of files to devices (specify anywhere in the file system to write). There are cases where the main HBAction running thread gets stuck or crashes. Some way to reboot that thread (perhaps automatically on the reset message). Ditto with the main OSC broadcast listener thread. Any others? Perhaps reset needs to completely rebuild the class? Perhaps reset should NOT clear the store field. Not that this is really being used. Implement a series of timestamped event routines, given that we have NTP working very nicely now. doAtTime(). Some basic maths for calculating future beat times. A standard protocol for sending tempo/beat schedules into the future (e.g., plan and share a list of beat, tempo and event-time tuples?).