Repeating a function every minute

function functionThatsRun()
--code you want to repeat here
print("it has been 60 seconds")
end
while true do
functionThatsRun()
sleep(60)
end

jay5476, on 20 October 2013 - 02:48 AM said:

try learning a bit more the reference manual and PIL are great but here's a piece of code you can use

function functionThatsRun()
--code you want to repeat here
print("it has been 60 seconds")
end
while true do
functionThatsRun()
sleep(60)
end

function functionThatsRun()
  -- code you want to repeat here
  print("it has been 60 seconds")
end

function functionThatKeepsRunning()
  -- Your code
  print("I'm also running")
end

local function F1()
  while true do
    functionThatsRun()
    sleep(60)
  end
end

parallel.waitForAll(F1, functionThatKeepsRunning)

alakazard12, on 20 October 2013 - 01:16 PM said:

And if you want to also run something else at the same time, you can do something like this:

function functionThatsRun()
--code you want to repeat here
print("it has been 60 seconds")
end

function functionThatKeepsRunning()
-- Your code
print("I'm also running")
end

local function F1()
while true do
functionThatsRun()
sleep(60)
end
end

parallel.waitForAll(F1, functionThatRuns)

function functionThatsRun()
  --# code you want to repeat here
  print("it has been 60 seconds")
end

function functionThatKeepsRunning()
  --# Your code
  print("I'm also running")
end

local function F1()
  while true do
    functionThatsRun()
    sleep(60)
  end
end

parallel.waitForAll(F1, functionThatKeepsRunning)

alakazard12, on 20 October 2013 - 01:16 PM said:

jay5476, on 20 October 2013 - 02:48 AM said:

try learning a bit more the reference manual and PIL are great but here's a piece of code you can use

 function functionThatsRun() --code you want to repeat here print("it has been 60 seconds") end while true do functionThatsRun() sleep(60) end 

And if you want to also run something else at the same time, you can do something like this:

 function functionThatsRun() --code you want to repeat here print("it has been 60 seconds") end function functionThatKeepsRunning() -- Your code print("I'm also running") end local function F1() while true do functionThatsRun() sleep(60) end end parallel.waitForAll(F1, functionThatRuns) 

while true do
  function_you_want_to_repeat()
  sleep(60)
end

awsmazinggenius, on 20 October 2013 - 11:04 PM said:

Scrolled to bottom immediately, so sorry if this was already answered.

while true do
  function_you_want_to_repeat()
  sleep(60)
end

slugy12345, on 23 October 2013 - 06:39 AM said:

-snip-

function func()
--code
timer = os.startTimer(60)
end

func()

while true do
event = os.pullEvent()
if event == "timer" then
  func()
end
end

MR_nesquick, on 23 October 2013 - 05:35 PM said:

you can also use os.startTimer if you want the computer to "multitask" without using parallel…

• It's almost always better to use local variables as to not pollute the global namespace. It can be speedier in some cases as well.
• I would exclude the timer from the func() function to separate looping and action logic and implement the timing entirely in the looping section of the code. With that in mind, I would also use a "period" variable that can easily be edited for ease of tweaking and to suit multiple use cases.
• The code compares the wrong parameter with the timer object.

local function func()
 --code
end

local period = 60
local timer = os.startTimer(period)
while true do
 local event, p1 = os.pullEvent()
 if event == "timer" and p1 == timer then
  func()
  timer = os.startTimer(period)
 end
end

MR_nesquick, on 23 October 2013 - 06:04 PM said:

#1. ofc, but none of my naming is used globaly
#2[1]. you can, but in your case you need to wait 1 min for the program to start
#2[2]. you can do that, but the OP asked about 1 min
#3. ??? param is used if you're running multiple timers

Kingdaro, on 23 October 2013 - 06:20 PM said:

The one of the problems with global naming is the potential of being run by another program that uses the same global variable. The variable can change to an unexpected value and even an unexpected value type, and can cause errors through conflict. It can be fair to assume that any programs you're using are created by you and are run under your systems, but keeping track of variable names to avoid conflict can become a massive headache.

function shell.run( sPath, ... )
    local sPath = ( type( sPath ) == "string" and sPath or error( "String expected, got " .. type( sPath ), 2 )
    if fs.exists( sPath ) then
       local file = fs.open( sPath, "r" )
       local content = file.readAll()
       file.close()

       local func, compileError = loadstring( content, fs.getName( sPath ) )
       if func then
          setfenv( func, getfenv(3) )
          local ok, runtimeError = pcall( func, ... )
          if not ok then
             error( runtimeError, 2 )
          end
          return true
       else
          error( compileError, 2 )
       end
   else
       error( "File not found", 0 )
   end
end

local function run( _sCommand, ... )
	local sPath = shell.resolveProgram( _sCommand )
	if sPath ~= nil then
		tProgramStack[#tProgramStack + 1] = sPath
   		local result = os.run( tEnv, sPath, ... )
		tProgramStack[#tProgramStack] = nil
		return result
   	else
    	printError( "No such program" )
    	return false
    end
end

local function runLine( _sLine )
	local tWords = {}
	for match in string.gmatch( _sLine, "[^ \t]+" ) do
		table.insert( tWords, match )
	end

	local sCommand = tWords[1]
	if sCommand then
		return run( sCommand, unpack( tWords, 2 ) )
	end
	return false
end

function shell.run( ... )
	return runLine( table.concat( { ... }, " " ) )
end

MR_nesquick, on 23 October 2013 - 06:04 PM said:

#1. ofc, but none of my naming is used globaly

MR_nesquick, on 23 October 2013 - 06:04 PM said:

#3. ??? param is used if you're running multiple timers

Kingdaro, on 23 October 2013 - 05:44 PM said:

It's almost always better to use local variables as to not pollute the global namespace. It can be speedier in some cases as well.