YES! Add me to the whish-list!
And when you start with that, do not forget the LUT which woud become more clear at first sight when the in- and output names could be choosen freely.
Good point about the LUT, I hadn't used one in a while so I forgot about that, but it would be extremely helpful there as well. I remember getting very confused a couple of times with my BLDC commutation table about which input was the direction input and things like that.
I see no reason why we'd NOT do this. Just enable you guys to name the bits and generate #define macros so that the APIs are easier to use. I'll add this request to our list.
Thanks for the suggestions - but I obviously cannot comment on a timeline to address this.
Good call, macros would make it even better. I was just thinking of printing the name on the schematic so that someone can read the schematic more easily, but if the same name is used in the code that is obviously even better.
I wasn't pressing for a time commitment, just raising it as a nice to have for v.Next.
Hey, that is music in my ears! I'm eager waiting for to update my old projects as long as I still remember what the bits were for!