Hi – thanks for opening this issue.

I'm not convinced yet that making the immutable properties of a GIF writable is the best way to go. Consequently, the same would have to happen e.g. with delay times.

Here is an approach with a loop completion block: https://github.com/Flipboard/FLAnimatedImage/pull/60/files

I'll think more about it. Any input is welcome!

#60 seems like a natural fit. Any chance to merge it?

I would second making the loop count and delay times writable. I tried several different methods to make a gif not loop. It works in a browser, but not in FLAnimatedImage.
I'm not placing any blame in FLAnimatedImage, because GIF is perhaps a more complex standard than is reasonable.

But it would save a great deal of hair-pulling if I could just set an integer property, instead of wrestling with command-line tools that cater to an arcane spec.

+1

@x1024 I solved with a simple workaround. After each loop is finished, it calls the loopCompletionBlock on the FLAnimatedImageView instance. I have simply implemented it like

private func finishedLoop(remainingLoops: UInt) {

    imageView.stopAnimating()
}

@dalu93 How to use loopCompletionBlock in swift 3?

@dalu93
In swift 3
self.imageView.loopCompletionBlock = { (uint: UInt) -> Void in
// unit is the loop time of image.
self.imageView.stopAnimating()
}