What are your thoughts about including the timer object in the block?

public class func every(interval: NSTimeInterval, _ block: NSTimer -> Void) -> NSTimer {}

Otherwise I need to declare the variable separately like this:

var timer: NSTimer?
timer = NSTimer.every(5.seconds) {
    timer?.invalidate()
}

I was wondering if you can clarify what the difference is between

NSTimer.every(0.7.seconds) {
    println(self.status)
}

and

let timer = NSTimer.new(every: 1.second) {
    println(self.status)
}

Thanks for sharing your work. Trying to do something apparently simple but I see nothing on the console and breakpoints don't stop there. What am I getting wrong?

let backgroundQueue = DispatchQueue(label: "1sec",
    qos: .background,
    target: nil)

backgroundQueue.async {
    Timer.every(1.seconds) {
        self.log.debug("Timer tick at \(Date())")
    }
}

Cheers

I haven't perused the source fully, but I would imagine there is no reason that 10.11 is the deployment target for this. I'm wanting to use it in a project that needs to support mavericks. My guess is it was an oversight, as it was in my project file.

When I call a NSTimer.after and pass a function, it doesn't have a argument name for second argument. This feels not natural for me regarding that all other functions usually used default or external names.

  NSTimer.after(1.second, close)

Using default names don't change the nice trailing closure syntax

public class func after(interval: NSTimeInterval, block: () -> Void) -> NSTimer 
...
NSTimer.after(1.second) {
  print("done")
}

If you agree I can make a PR :)

@radex

Fixes https://github.com/radex/SwiftyTimer/issues/27

Most of the migration was done using Xcode's migration tool. It is mostly about renaming NSTimer to Timer.

Minor thing to note: Swift 3 will now produce a warning of the result of Timer.<method> is unused.

Let me know if you have any question.

Swift Package Manager

• iOS: Open Xcode, File->Swift Packages, search input https://github.com/radex/SwiftyTimer.git, and then select Version Up to Next Major 2.1.1 < .
• Or add dependencies in your Package.swift:

.package(url: "https://github.com/radex/SwiftyTimer.git", .upToNextMajor(from: "2.1.1")),

Please git a new tag to support it.

This was required in my project to be able to use after and every methods for timers that need to update the UI. The timer needs to run in .commonModes to be able to update the UI while scrolling.

It keep the same behaviour as previously and the signature is backward compatible. I added a new start function because the splat operator is not available in Swift, hence the need to create a new one that takes an array as parameters.

Feedbacks are welcome, I will adjust the PR accordingly.

Hello!

I want to make a function that starts the timer unless there is a bool true in params (e.g. animateStatusIcon(stop: true)) - in that case I want to stop the timer. Does anyone have an idea what's going on here?

The timer starts but no matter what I do it wont stop.

func animateStatusIcon(stop: Bool? = nil){
        
        let icon = NSImage(named: "statusIcon")
        let iconActive = NSImage(named: "statusIconActive")
        
        let timer = Timer.every(0.4.seconds) {
            self.statusItem.image = icon
            Timer.after(0.2.seconds) {
                self.statusItem.image = iconActive
            }
        }
            
        if(stop == true){
            print(stop!)
            print("should stop now")
            timer.invalidate()
        } else  {
            print(stop)
            print("start")
            timer.start()
        }
        
    }

The following code worked with 1.3.0 but crashes with 1.4.0:

let timer = NSTimer.every(1) { 
            print("do something!")
        }
timer.fire()

The internal refactoring of not using NSTimer initializers might be the problem.