Hi, I would really like to use GuageKit in an upcoming project, as it will make my life much easier in designing some cool gauges. Tried importing it into my new project and there are 56 errors, mostly related to changes Apple made in Swift 3. Do you have plans on updating GuageKit for iOS 10? Is there any plans for GuageKit on WatchOS 3? Do you have a version you are testing for iOS 10 Beta, that I may be able to get access to early? Thank you very much in advance. I have been looking all over for this type of Pod, and this helps a lot, assuming you plan to update it for iOS10.

Basically everything happens in :

• Gauge+Animations.swift (new file)
• MainViewController.swift (changed)

And I had to add two variables :

• animationTimer
• animationCompletionBlock

Now, I absolutely DON'T get the easy part of the job, shame on me... I don't get how to update the framework in the example. So the example won't compile for now. I was not able to test the final result, but it should work no problem.

It's subtask of #12.

I start working on it in gradientCircle branch, but implementation is not quite easy and still have issues.

Also - it looks not very well without overlapping (the border of startColor and endColor). I want to find solution, that can fix this and #12 issue at once.

Hi I am displaying the gauge in CellForRowAtIndexPath and I tried changing the color of gauge depending on its value this is my actual code of doing it

if result! > 0 && result! < 26 { cell.gauge.startColor = UIColor.redColor() cell.gauge.endColor = UIColor.redColor() } else if result! > 25 && result! < 51 { cell.gauge.startColor = UIColor.orangeColor() cell.gauge.endColor = UIColor.orangeColor() } else if result! > 50 && result < 76 { cell.gauge.startColor = UIColor.yellowColor() cell.gauge.endColor = UIColor.yellowColor() } else { cell.gauge.startColor = UIColor.greenColor() cell.gauge.endColor = UIColor.greenColor() }

but it doesn't seem to work it keeps displaying the color i set in mainStoryBoard. The if condition works fine it reads the code in each scenario but it doesn't render the color I need.

Hey, first of all thank you for this project.

What I need you to help me think is how can I implement a maxValue feature like a UISlider so if I have a timer it goes and finish at the same time as the timer or if there's a way already can you be so kind to explain how to implement it because rate works perfectly but I need to increment de Gauge proportionally a Timer I have.

Let me know if you need more context and thank you very much for your help.

Is it possible to smaller arcs? I want to try to do a series of arcs on the same path. First segment say 10degrees, then a gap, then a new segment of 40degress, then a small gap and then another segment.

Or simply point me to how to creat say a 20 degree arc. Both ends need to be rounded so I can’t just turn it white for thev160 degrees left.

Thank you

I know that is too early to ask, but we are with a little problem on GaugeKit in iOS 12 using Xcode 10 beta. The GaugeKit was working fine in my app until the last version, but when I updated to iOS 12 and Xcode 10, the app doesn't compile anymore.

This is what I receive from xcode. Showing Recent Messages :-1: Multiple commands produce '/Users/…/Library/Developer/Xcode/DerivedData/…/Build/Products/Debug-iphoneos/GaugeKit/GaugeKit.framework/Info.plist':

1. Target 'GaugeKit' has copy command from '/Users/…/Desktop/…/Pods/GaugeKit/GaugeKit/Info.plist' to '/Users/…/Library/Developer/Xcode/DerivedData/…/Build/Products/Debug-iphoneos/GaugeKit/GaugeKit.framework/Info.plist'
2. Target 'GaugeKit' has process command with input '/Users/…/Desktop/…/Pods/Target Support Files/GaugeKit/Info.plist'

Could you help me?

Hello, thanks for this very useful project. For making it compatible with Swift 4 you just needs to do the following modification :

In file Gauge+Animations.swift the function: func updateProgress(_ timer: Timer) -> Void needs to have @objc to respond to the selector: @objc func updateProgress(_ timer: Timer) -> Void

Hi, I would love to use your beautiful control, but I can't get it to work. I used CocoaPods for importing it, then add @objc in the method requested for swift 4 support. But then I get this error:

../Main.storyboard: error: IB Designables: Failed to render and update auto layout status for ProvaViewController (Rn0-yv-HO4): dlopen(GaugeKit.framework, 1): no suitable image found. Did find: GaugeKit.framework: required code signature missing for 'GaugeKit.framework'

Can you help me please?

This patch will correctly blend colors for gauges with multi-color array defined. There was a problem using the average of the Int-value of colors. The red, green and blue values needed to be averaged separately. Also, since this is correct now, the same mechanism works for 1, 2 and more colors.

pod spec lint

 -> ZMAppFoundation (0.1.5)
    - ERROR | [iOS] xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - ERROR | xcodebuild:  GaugeKit/GaugeKit/Gauge+Animations.swift:22:23: error: argument of '#selector' refers to instance method 'updateProgress' that is not exposed to Objective-C
    - NOTE  | xcodebuild:  GaugeKit/GaugeKit/Gauge+Animations.swift:32:10: note: add '@objc' to expose this instance method to Objective-C

Analyzed 1 podspec.

I have a cocoa pod that uses gauge kit as a dependency (https://github.com/jfosterdavis/ZMAppFoundation/tree/release-0.1.5). When I am doing local development I change line Gauge+Animations.swift:32:10 from: func updateProgress(_ timer: Timer) -> Void { to @objc func updateProgress(_ timer: Timer) -> Void {

When using a circle gauge (type4) the end color is ignored. This can be seen in the example app where the innermost gauge has a start and end color but is locked to the start color.

This may be intentional since the ends coming together is probably strange with two colors but I wanted to confirm before we changed our UX.

This tools is so great. Thanks!

As Dave mention in iOS Dev Weekly - Issue 205.

It doesn't do the fancy overlapping rings

So, he is definitely right! It should be implemented in next release!