6 replies to this topic

[surferpup]

I have figured out that this doesn't work, but why doesn't it work?

while true do
  parallel.waitForAny(os.pullEvent("key"),os.pullEvent("rednet_message"))
  print("Something Happened.")
end

I know I can work around this issue by setting up one pullEvent and then going through and testing the event. But I thought this would set up two "threads" and allow me to work off of whichever triggered first.

Edited by Lyqyd, 30 January 2014 - 10:39 AM.

[CometWolf]

I already explained this to apples, you can't pass any arguments directly to the functions you're running in parallel.

Edited by CometWolf, 30 January 2014 - 01:01 AM.

[surferpup]

Okay. I actually simplified the code for purposes of the question. Here is my actual code -- sorry if I caused confusion:

local event,message,sender,key
local function getRednetEvent()
    sender,message,_ =os.pullEvent("rednet_message")
    event="rednet"
end
local function getKeyEvent()
    key,_ =os.pullEvent("key")
    event = "key"
end
while true do
    parallel.waitForAny(getKeyEvent(),getRednetEvent())
    print (event)
end

I am not passing any arguments.

[Grim Reaper]

Your code doesn't work because the functions execute in the parameters of your call to the parallel API, meaning that you're calling the parallel API with whatever is returned by those functions. You have to actually pass the functions themselves to the parallel API so that it can create threads out of them and run them for you.

So, you can change that parallel line to this:

parallel.waitForAny (getKeyEvent, getRednetEvent)

Also, the "rednet_message" event no longer exists, if I'm not mistaken. If you want to handle communications over rednet, you'll have to use "modem_message" to capture modem messages as that is the way rednet works now. You can still use the rednet functions, but they are actually using "modem_message" underneath.

Edited by Grim Reaper, 30 January 2014 - 01:13 AM.

[theoriginalbit]

Okay so this is a perfect thread for you, particularly my reply.

also it should be noted that Coroutines do not run at the same time, so this

surferpup, on 30 January 2014 - 12:55 AM, said:

But I thought this would set up two "threads" and allow me to work off of whichever triggered first.

may not have the intention you're hoping for. actually its a pointless use of coroutines, just setup an event loop that checks the events.

Grim Reaper, on 30 January 2014 - 01:11 AM, said:

Also, the "rednet_message" event no longer exists, if I'm not mistaken. If you want to handle communications over rednet, you'll have to use "modem_message" to capture modem messages as that is the way rednet works now. You can still use the rednet functions, but they are actually using "modem_message" underneath.

You are mistaken, the rednet_message event still exists for backward compatibility, there is a rednet coroutine running with the shell that translates modem_message into rednet_message

Edited by theoriginalbit, 30 January 2014 - 01:16 AM.

[CometWolf]

Ditch the brackets in the parallel function calls. You don't want to actually call them, just pass them as variables.

Edit: much ninja, so skill

Edited by CometWolf, 30 January 2014 - 01:16 AM.

[surferpup]

You folks are awesome, and I am an idiot. I get it. By using getKeyEvent() with parenthesis, I was not passing a pointer to a function. By removing the parenthesis, I pass a pointer. Fixed that, fixed the code.

[SOLVED] with the help of an amazing coding community

Edited by surferpup, 30 January 2014 - 01:17 AM.