adafruit on Nostr: It's fast! And has very few errors. We like to go through each register one by one, ...
It's fast! And has very few errors. We like to go through each register one by one, add the typedefs and #defines, then the setter/getter functions, and finally the arduino ino 'sketch' to actually test and verify. However, with three files - header, cpp, and ino - canvas can get really confused about which file we're editing and what it's called.
Published at
2024-10-08 18:14:11Event JSON
{
"id": "0aef0d841e27c41f0bb412bb661a6b9b3ffb789a318af88c4e9da5072d23285e",
"pubkey": "c164633a8802f15a960409c6a2889f36b63295baf91bdad19dfdaf1db4cef46a",
"created_at": 1728411251,
"kind": 1,
"tags": [
[
"e",
"b83ddec6a13266eb3a81984dd04b44256938ff218f1e84c0d5b06ae3b1ed3561",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"defines"
],
[
"proxy",
"https://mastodon.cloud/users/adafruit/statuses/113273159764345988",
"activitypub"
]
],
"content": "It's fast! And has very few errors. We like to go through each register one by one, add the typedefs and #defines, then the setter/getter functions, and finally the arduino ino 'sketch' to actually test and verify. However, with three files - header, cpp, and ino - canvas can get really confused about which file we're editing and what it's called.",
"sig": "0cb416948af4b19757fdf83493a77fb339f75c51a732b40cc6bf34d5e9ccc0593e0bf7bc6f1a5f91965801115c8d8ecf3d5b1d1accc23490e85bcf954c6b7ffc"
}