@Jeremy_Spencer so the animations are doing the same thing with slant on always and the others flashing with corresponding buttons when I hit the button- do I need to change it to when the button is “released” instead of pressed?
That didn’t change anything. Jason Coon said I should manually set the mode- what does that involve?
I’d use the heart shaped map, “ledArray”
Change line 219 in effect.h to
int pixel = ledArray[(x, y)];
if (pixel>-1){
leds[pixel]= CHSV(gHue, 255, quadwave8(x * 32 + y * 32 + slantPos));
}
And see if that gets your slant pattern working…
line 233 in xymatrixdemoBLE.ino should probably be
if (mode == 2 && pressed == true)
This will make it check that a button has actually been pressed, rather than just the last button pressed.
But this may not give you the results you want…It may actually work better as it is, but then the comment is wrong 
@Jason_Coon meant that you should comment out lines 233 to 262, taking all of the button control out. But leave in the three lines for the pattern you are testing. For example leave lines 258,259,260 for slant bars
This is a very sensible way forward as you can ensure that all of your patterns are working properly.
Looking at the plasma animation, try replacing line 59 in effects.h with
int pixel = ledArray[(x, y)];
if (pixel>-1){
leds[pixel] = CHSV(color, 255, 255);
}
oh weird my app wasn’t updating all of your comments. I am going to torch all of my apple products… ok I’m going in to look at your last couple suggestions
I’m using a surface pro, same problem. But I am allergic to Apple
Don’t make this change
“if (mode == 2 && pressed == true)” or the code will only call the pattern while you are holding the button…
I think that some of the weird button related behaviour probably comes the patterns calling leds that don’t exist. Make the changes to the patterns and the button code may come good
just for fun, this was my matrix mapped led project this morning https://photos.google.com/share/AF1QipNRKDSgCyQQVIQCjeGpemf7i3pg9SNOpg6dKtYUAQaQ4E9SfvwY-m-Ul4M_fHuDVg?key=dGNkUExnc3NtSUg5cmpjOC11eC1aYnJMaUJRc21R (81 APA102s)
and last weeks https://photos.google.com/share/AF1QipPCVk1MDCpAUVMVxYwbY43TPeGjAByNcTXoVFk1g9jmhKeeZqCRI3CT04LnoWOo5g?key=amU4UTFzV2Vfb2VJbEZwSjJmNlB5WjZGM0pFdzZB (400 WS2811s)
and tomorrows https://photos.google.com/share/AF1QipMmPaTZ7peF5sFhxPEgHmbiyg2AASz1jvtVVsTMMad0bctqD1mYwHk9_aU1TSbwgw?key=cHBGNmpRTjd5VUZWdWFMd0M5ME9aWkZYZlNIVnd3 (about 270 APA102s, I’ve not mapped them yet)
And if it makes you feel better, I was still writing the code for the net/strings while the band were setting up…
Wow awesome!
When the four patterns are working, try printing the mode at line 232 of xymatrixdemoBLE.ino
So I’m trying to switch over the map but having an issue. First off all of the animations work well in a different sketch with no BLE. So I know that they like the Kreigsman xymap. The one in the original RGB sketch also only calls up strip animations which is weird.
@Jeremy_Spencer haha re:writing code while band set up! 2 weeks ago the data line popped out as I was dressing the performer to go on in 5 mins. They had to stall so my soldering iron could heat up! That was a very slapped together situation though- never again!
Always glue the connections too, goop is great, and you can get it off again if you have to, but the fumes are nasty
Try commenting out the button code, and just leave the pattern you want then
next time use @Jason_Coon 's wemos mini d1 web control app. He posted it on here…
Are the patterns correct with the Kreigsman xymap? That looks as though it’s for the shades rather than your project…
ok so now replacing the .show and .delay(1000/framerate) in each button has fixed the issue with the slant showing on all. but the animations still only advance if i hot them a buch of times quickly. I’m about to just add a real button and get this thing sewn up - I have to do a leather mini skirt too!
oh yeah he actually wrote the code for the shades I think - I left it as shades since I was using this particular code