diff options
| author | khonkhortisan <kyle.kylina@gmail.com> | 2012-08-21 10:35:34 -0700 |
|---|---|---|
| committer | khonkhortisan <kyle.kylina@gmail.com> | 2012-08-21 10:35:34 -0700 |
| commit | 68b99fed764d6886b4f44254aa26c60300e8e6b0 (patch) | |
| tree | ed7cbb7eb76bdb3da2fb8e2839fc1a7903c532ce /README | |
| parent | 15fa38b848c016f6b3404cd8428b2517a3e00984 (diff) | |
| download | mesecons-68b99fed764d6886b4f44254aa26c60300e8e6b0.tar mesecons-68b99fed764d6886b4f44254aa26c60300e8e6b0.tar.gz mesecons-68b99fed764d6886b4f44254aa26c60300e8e6b0.tar.bz2 mesecons-68b99fed764d6886b4f44254aa26c60300e8e6b0.tar.xz mesecons-68b99fed764d6886b4f44254aa26c60300e8e6b0.zip | |
display µc programming like a sign
I had a grid that mapped buttons to pixels so pressing a button displayed a letter. I had one programming that was a positive match so the pixel turned on, and another programming that was negative and just passed the signal on to the next pixel. If I had to right-click on each µc to see its programming, it would take me longer to find a problem. If I can see the programming just by looking at it, I could find a typo much easier.
I'm not sure about the \n \n\r thing.
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions