mesecons/mesecons_luacontroller, branch origin/zefram_doors

Fix #155 (option 2 used). Remove non-ActionQueue system. Enable overheat for more than 20 actions per second on lua- / microcontrollers and gates.

2014-04-20T19:51:17+00:00

Fix a bug where a burnt luacontroller didn't have the correct pin-states as the burnt controller does not register any changes from outside.

Fix #83 (experimental)

2014-03-19T13:47:22+00:00

Why did we actually put the update action in a queue again? Whatever issue it that was for, I couldn't reproduce it. Propably the ActionQueue fixed that...?

Remove timer() from LuaController and make interrupt() use the ActionQueue so that it will keep working when restarting the server

2014-03-19T09:20:43+00:00

Improve and clean up luacontroller digiline_send on globalstep feature

2014-03-19T08:11:07+00:00

Merge branch 'digiline-non-reentrant' of https://github.com/CiaranG/minetest-mod-mesecons into CiaranG-digiline-non-reentrant

2014-03-16T20:12:50+00:00

Conflicts: mesecons_luacontroller/init.lua

Merge pull request #152 from CiaranG/timer

2014-03-16T20:05:49+00:00

Add timer() function/event (node timer based) to luacontroller

2014-03-11T22:50:48+00:00

This adds a timer() function, which causes an event of type "timer" to be fired after that many seconds has elapsed. Because it's node timer based, it works properly across server restarts and block unloading. Thus, simplest example, a blinky plant replacement with a 10 second period: if event.type == "program" then timer(10) elseif event.type == "timer" then port.a = not port.a timer(10) end

Handle luacontroller formspec events correctly

2014-03-11T17:54:56+00:00

Example of problem fixed by this: Edit lua code, press Execute. Now (execute button has focus), hold down a key. Zillions of "program" events are generated.

Send digiline messages after luacontroller execution

2014-03-11T17:34:30+00:00

In the same way as for port settings, this queues up digiline messages sent during the luacontroller's execution, and sends them afterwards. This solves many problems, but one example: 1. Send a message, and receive a reply from another device. 2. While handling the reply event (effectively a nested invocation on the same luacontroller) make a change to memory 3. Notice that the memory change has no effect, because after completion of the reply handling, it stores the memory, but then the original invocation completes and overwrites it with it's own earlier copy of the same memory.

Add missing string.upper to luacontroller

2014-02-16T13:28:07+00:00