Easy Haptic Feedback Generator 📳

There is no real issue and this topic is more of an observation type.

Q.1: I used Haptica as:

button.isHaptic = true // required call.
button.hapticType = .impact(.light) // optional, but has to be set.
button.hapticControlEvents = .touchUpInside // optional, default is .touchDown as per implementation.

My initialization logic has a flaw since button.isHaptic = true immediately triggers a call to addTarget() with .touchDown as default value (if hapticControlEvents is not set). Hence hapticControlEvents should be initialized before button.isHaptic = true invocation to make any effect.

Would this make sense to refactor and introduce methods like these:

func addHaptic(_ haptic: Haptic, forControlEvents events: UIControl.Event = .touchUpInside)
func removeHaptic()

to enable 1 line setup? Methods naming strategy 'addHaptic', 'removeHaptic' stolen from 'addTarget', 'removeTarget'.

Q.2: Does it make sense to implement Hapticable for UIControl rather than UIButton? (since addTarget and removeTargets methods implemented in UIControl). This would enable Haptics for elements like UISwitch.

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [x] I've updated the documentation if necessary.

Motivation and Context

Description

Checklist

• [ ] I've tested my changes.
• [ ] I've read the Contribution Guidelines.
• [ ] I've updated the documentation if necessary.

Motivation and Context

Description

New Issue Checklist

• [x ] I updated Haptica to the latest version.
• [x ] I read the Contribution Guidelines.
• [x ] I read the documentation.
• [x ] I searched for existing GitHub issues.

Issue Description

Title says it all.

Thanks!

Environment

• iOS Version: [any]
• Device(s): [any]

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [x] I've updated the documentation if necessary.

Motivation and Context

Two new types of feedback intensity in iOS13 which are not handled or mapped in Haptica.

Description

Added soft and rigid types of feedback and updated the example app.

Checklist

• [ ] I've tested my changes.
• [ ] I've read the Contribution Guidelines.
• [ ] I've updated the documentation if necessary.

Motivation and Context

Description

I am using Haptica in my app I recently release a new version of my app on 16 July after that repeating crashes are reported on Xcode organiser. Below are the exception details:-

ERROR: -[_UIFeedbackHapticOnlyEngine _deactivate] called more times than the feedback engine was activated

Fatal Exception: NSInternalInconsistencyException 0 CoreFoundation 0x1f7bc927c __exceptionPreprocess 1 libobjc.A.dylib 0x1f6da39f8 objc_exception_throw 2 CoreFoundation 0x1f7ae2988 +[_CFXNotificationTokenRegistration keyCallbacks] 3 Foundation 0x1f85a6188 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] 4 UIKitCore 0x224055628 -[_UIFeedbackEngine _deactivate] 5 UIKitCore 0x22403e58c -[UIFeedbackGenerator __deactivateWithStyle:] 6 libdispatch.dylib 0x1f7608a38 _dispatch_call_block_and_release 7 libdispatch.dylib 0x1f76097d4 _dispatch_client_callout 8 libdispatch.dylib 0x1f75b7004 _dispatch_main_queue_callback_4CF$VARIANT$mp 9 CoreFoundation 0x1f7b5ac1c CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE 10 CoreFoundation 0x1f7b55b54 __CFRunLoopRun 11 CoreFoundation 0x1f7b550b0 CFRunLoopRunSpecific 12 GraphicsServices 0x1f9d5579c GSEventRunModal 13 UIKitCore 0x2244cf978 UIApplicationMain 14 Qpay 0x102253268 main + 16 (GeneratePasscodeInteractor.swift:16) 15 libdyld.dylib 0x1f761a8e0 start

Haptica version:- 3.0.0 Thanks

'cannot assign to property' fix

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [ ] I've updated the documentation if necessary.

Motivation and Context

this change will solve cannot assign to property: 'self' is immutable error for cases when trying to assign property inside subclass c-tor

Sample code:

class MyButtonSubclass: UIButton {
    override init(frame: CGRect) {
        super.init(frame: frame)
        isHaptic = true
        hapticType = .impact(.heavy)
    }
}

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [x] I've updated the documentation if necessary.

Description

• Added Swift 5.0 Support

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [x] I've updated the documentation if necessary.

Description

Lowers the Deployment Target to 9.0 whereas for devices lower than iOS 10 it simply does nothing.

Checklist

• [x] I've tested my changes.
• [x] I've read the Contribution Guidelines.
• [x] I've updated the documentation if necessary.

Motivation and Context

Library is hard/impossible to use via carthage if the host project has a Deployment Target of 9.0. I do know that inside the CONTRIBUTING.md it is stated to not lower the deployment target. But still, I would prefer to at least have the option to use the framework and add extra functionality with ease for my users that are >=iOS 10.0 without any hassle.

Description

Lowers the Deployment Target to 9.0 whereas for devices lower than iOS 10 it simply does nothing.

How to stop while playing a long pattern

Haptic.play("OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO", delay: 0.1)

I want to stop this when this is playing. Please show me a way to do it.

thanks

I tried with the following pattern but nothing simulates a double tap, how do I do that?

addButton(pattern: "O") addButton(pattern: "o") addButton(pattern: ".") addButton(pattern: ".-.") addButton(pattern: "o-o") addButton(pattern: "O-O") addButton(pattern: "..oO-Oo..") addButton(pattern: "O--O") addButton(pattern: "o--o") addButton(pattern: "o---o") addButton(pattern: "O---O") addButton(pattern: "o--O--O--o") addButton(pattern: "o--O---O--o") addButton(pattern: "O--O---O--O") addButton(pattern: "OOO------------------------OOO")

Thanks for this great library!

I'm trying to use it in a table view, and I have the following code:

func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
  Haptic.impact(.medium).generate()
  // Other stuff...
}

This generates haptic feedback, but sometimes it seems to be generating two very fast consecutive ones. It happens when you click on one cell and then another.

Is it the wrong way to use the library? Thank you!