You said there were a lot of methods, the tool made 154 method patches.
But, all of the patches have an error, because we failed to make the constructor, because the only constructor takes a pointer, so I skipped it.
This class has public instance variables!
Error4D, etc. I turned off that code in my tool because I don’t know what patch(s) to produce. What should I generate? A getter (pulse to trigger)? A setter (like any other state-change-patch: pulse to trigger, output pulse?)?
Should probably figure out a mapping of XOD’s string to some useful type (
const char seems hard)? It’s not clear which/what we should do:
It occurs to me that we are doing a trivial wrapping of the “native” method. I’ve forgotten if there is a way to have c++ inline the actual method (and avoid the second call)?
picaso-serial-arduino-library-ll.xodball (566.0 KB)