yep, crazy. Sorry, I don’t have MaxO so I can’t really test for you. Someone who also has one will need to pipe up I think, or we could crack open the driver for a lookee… Codeplex here I come (while waiting for Simon Monk’s Gadgeteer webcast to start)
What is not making any sense to me is that the code literally manages a private byte array that is a copy of what is sent. If you use WritePin(), you end up affecting the private byte array, which then gets written using the WriteArray method anyway. So I can’t imagine a scenario where WriteArray is not doing the right thing but WritePin is (although I haven’t stepped in through the logic WritePin uses to manipulate the specific byte). Can you grab the code and try stepping into it and seeing what the array looks like just before the SPI write?