mitchmindtree

DAC point memory layout in protocol differs from implementation in physical DACs

1

The protocol specifies the layout as of DAC points as `control, x, y, i, r, g, b, etc`, however physical DACs seem to expect this order instead: `control, x, y,...

Currently very little effort has gone into the realism of the DAC emulator and I likely won't spend any further time on it. That said, if anyone would like to...

Add a tutorial for working with audio streams

1

Here are some comments related to sharing data between the GUI and audio threads I recently shared with another nannou user on slack - they might be useful to add...

This can be copied from `nannou-org/nannou/CODE_OF_CONDUCT.md`.

A reminder to re-add the following job once [this upstream issue](https://github.com/NixOS/nix/issues/4265) is resolved: ```yaml nix-flake-check: needs: cancel-previous-runs runs-on: ubuntu-latest steps: - uses: actions/[email protected] - uses: cachix/install-nix-action@v16 with: nix_path: nixpkgs=channel:nixos-unstable -...

Follow-up to #61, similar to what we have at the sway repo: https://github.com/FuelLabs/sway/blob/master/.github/workflows/markdown-lint.yml

Follow-up to #61 and #66.

The `mkPackages` function and `patches.nix` both make some assumptions based on the expectation that packages being built are Rust packages. This is fine for all fuel-core, sway and indexer packages,...

Consider using a distinct `forc-workspace.toml` manifest for workspaces

1

As raised by @Braqzen on Slack, the role of `Forc.toml` can appear quite ambiguous to new users, particularly users not coming from the Rust ecosystem. As of the introduction of...