Our designers often want to indent between the letters in the buttons. So I added support for this functionality in your library: setAttributedText("TEXT FOR STATE", for: .normal) setAttributedTextColor(.white, for: .normal) setAttributedTextSpacing(1.2) setAttribute(NSAttributedStringKey, value: Any, for: .normal) You can change button text with setAttributedText("ANOTHER TEXT FOR STATE", for: .normal) and all applied attributes refresh automatically.

Hello, In non autolayout view button's position is set to zero and size is minimized, removing this line of code fixes issue

Why do you have this? Can I break anything by removing it?

Cocoapods still references the old 2.1.1 version, rather than the latest (v3 as of writing this).

It would be much appreciated if this could be updated. For now I'll just change my Podfile to point at the latest tag.

https://cocoapods.org/?q=simplebutton

P.S. Thank you for this excellent Pod :)

I'm trying to enable a toggle feature through the selected property and using UIControlState.Selected for state. I get an extra blue layer in the background that I haven't been able to get rid off efficiently. Any tips?

The button doesn't appear as expected when subclassed and used with @IBInspectable variables to set up the values for configureButtonStyles like here:

import UIKit
import SimpleButton

@IBDesignable

class DesignableButton: SimpleButton {

        /// Background color for normal state.
    @IBInspectable var backgroundColorNormal: UIColor?
    @IBInspectable var backgroundColorHighlight: UIColor?
    @IBInspectable var titleColorNormal: UIColor?
    @IBInspectable var titleColorHighlighted: UIColor?

    @IBInspectable var shadow: Bool = false
    @IBInspectable var shadowColor: UIColor?
    @IBInspectable var shadowOffset: CGSize = CGSizeZero
    @IBInspectable var shadowRadius: CGFloat = 0
    @IBInspectable var shadowOpacity: Float = 0

    override func configureButtonStyles() {
        super.configureButtonStyles()

        if let backgroundColorNormal = backgroundColorNormal {
            setBackgroundColor(backgroundColorNormal, forState: .Normal)
        }
        if let backgroundColorHighlight = backgroundColorHighlight {
            setBackgroundColor(backgroundColorHighlight, forState: .Highlighted)
        }
        if let titleColorNormal = titleColorNormal {
            setTitleColor(titleColorNormal, forState: .Normal)
        }
        if let titleColorHighlighted = titleColorHighlighted {
            setTitleColor(titleColorHighlighted, forState: .Highlighted)
        }

        if shadow {
            if let shadowColor = shadowColor {
                setShadowColor(shadowColor)
            }
            setShadowOffset(shadowOffset)
            setShadowRadius(shadowRadius)
            setShadowOpacity(shadowOpacity)
        }
    }


}

You can reproduce this by adding the following line to the sample project:

        let awesomeButton = SimpleButton.buttonWithType(.Custom) as! SimpleButton
        awesomeButton.enabled = false //add this

If you run the project with that line in place, you will see that the awesomButton is not visible. Its attributes are set properly, but it hasn't been updated visually.

The problem is caused by the following check:

    if state == self.state

When you call e.g. setBackgroundColor, and button's state is .Disabled, but the attributes are set for .Normal. Thus, the method changeBackgroundColorForStateChange is not called and the button's appearance is not updated.

I wasn't sure if the above check is needed for performance reasons or if you can just get rid it.

• Adds default values for animated and state properties (default false)
• Access control: make set... methods private
• adds @IBDesignable and @IBInspectable attributes to be nicely displayed in Interface Builder
• change configure() to configureButtonStyles(): configure() feels a bit too generic to me, I think configureButtonStyles() will be clearer to other developers in the future.
• Updated the Readme (wordings, new features like @IBDesignable)
• Updated some project settings and added the SimpleButtonTests target (tests still need to be written)

Summary

The current Podspec is outdated, not reflecting the latest changes in the repository, such as the migration to Swift 5 and the version bump to 5.0.0.

With this pull request, the .podspec will be up to date.

Linter

❯ pod spec lint --allow-warnings

 -> SimpleButton (5.0.0)
    - WARN  | source: The version should be included in the Git tag.
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | xcodebuild:  note: Building targets in parallel
    - NOTE  | xcodebuild:  note: Using codesigning identity override: -
    - NOTE  | xcodebuild:  note: Build preparation complete
    - NOTE  | [iOS] xcodebuild:  note: Planning build
    - NOTE  | [iOS] xcodebuild:  note: Analyzing workspace
    - NOTE  | [iOS] xcodebuild:  note: Constructing build description
    - NOTE  | [iOS] xcodebuild:  warning: Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the App editor. (in target 'App' from project 'App')
    - NOTE  | [iOS] xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file and one is not being generated automatically. (in target 'App' from project 'App')

Analyzed 1 podspec.

SimpleButton.podspec passed validation.

Closes: #28

Cocoapods(https://cocoapods.org/pods/SimpleButton) still references the old 4.0.1 version, rather than the latest (5.0).

It would be much appreciated if this could be updated.

Thank you so much!

At present, the control completely blows VaryForTrait away. I think it is moderately easy to enable, but will have to review the Apple vids to confirm. This makes the corner radius attribute useless for a properly proportioned multi-device app.

If time permits, i will see if I can make it aware, then post back here, else (due to time constraints) will just tweak my deliverable to miss the mark as minimally as i can.