No, it actually does have to do with how the ledwiz (and the interfaces you've given us) operate.
When most devices can't keep up they buffer their messages, the ledwiz doesn't.
I don't think anyone would expect the lights to stay in sync with the current game while a list is scrolling, but when it stops they would expect it to display the layout for the current game they've stopped on. The way the ocx is setup a person can't guarantee that unless code is put in to wait a while after the list has stopped and send the command a final time. So while scrolling it won't sync (none of them will) and when stopped you are going to have to send the command again.
I know this to be true because of the rapid transmission tests I did with my little test app. If you just happen to send a command while another command is being processed, it is ignored, meaning your last command (the important one) might not get through. Usually this isn't a big deal, but in time-sensitive instances like this, it might be.
In other words, like I said originally, there is no way the ledwiz can keep up.
Now keeping in mind that I don't have an io-warrior to play with, I do have the specs on it and it appears that mala uses direct communication, meaning that it doesn't have a ocx "middle man" that can miss messages while it is busy doing other things. Neither one would be able to stay perfectly in sync, but the io-warrior would do a better job if you insist on brining up the old "it's your fault, not the ledwiz" broken record you are so fond of.
