From 68b99fed764d6886b4f44254aa26c60300e8e6b0 Mon Sep 17 00:00:00 2001 From: khonkhortisan Date: Tue, 21 Aug 2012 10:35:34 -0700 Subject: [PATCH] =?UTF-8?q?display=20=C2=B5c=20programming=20like=20a=20si?= =?UTF-8?q?gn?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- mesecons_microcontroller/init.lua | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mesecons_microcontroller/init.lua b/mesecons_microcontroller/init.lua index 24434b8..f531853 100644 --- a/mesecons_microcontroller/init.lua +++ b/mesecons_microcontroller/init.lua @@ -142,9 +142,9 @@ function update_yc(pos) code = string.gsub(code, " ", "") --Remove all spaces code = string.gsub(code, " ", "") --Remove all tabs if yc_parsecode(code, pos) == nil then - meta:set_string("infotext", "Code not valid!") + meta:set_string("infotext", "Code not valid!\n"..code) else - meta:set_string("infotext", "Working Microcontroller") + meta:set_string("infotext", "Working Microcontroller\n"..code) end end