Hi, morizotter! I am using your framework TouchVisualizer in my app. But I found that I cannot get the touch locations from your framework. So I add a method called getTouches() in your extension to get touch locations. Hope you can accept this pull request, and update your CocoaPods version so that I can download it from CocoaPods directly. Best wishes!

The new version has a preblem,use of unresoled identifier "warnIfSimulator",and UIWindow does not hav e a member named swizle,anyone konw why?and I can not find TouchVisualizer.swift?

bug fix - stop removes all touch views from view and prevents new ones from populating ---- previously calling TouchVisualizer.stop() would not stop new touches from showing on the screen

bug fix - changing config in TouchVisualizer adjusts new and previously created TouchViews ---- previously if you set a new config (Example: you want touches to be a different colors in different views) any previously created touchViews would not update

New xcode 11.4 update produces these errors (using latest TouchVisualizer 3.1.0 cocoapod):

<...>/Pods/TouchVisualizer/TouchVisualizer/Visualizer.swift:153:13: Switch must be exhaustive
<...>/Pods/TouchVisualizer/TouchVisualizer/Visualizer.swift:153:13: Do you want to add missing cases?
<...>/Pods/TouchVisualizer/TouchVisualizer/Visualizer.swift:209:13: Switch must be exhaustive
<...>/Pods/TouchVisualizer/TouchVisualizer/Visualizer.swift:209:13: Do you want to add missing cases?

Changes that fix build errors, but may not be correct:

@@ -179,6 +179,10 @@
                 }
                 
                 log(touch)
+            case .regionEntered, .regionMoved, .regionExited:
+                log(touch)
+            @unknown default:
+                log(touch)
             }
         }
     }
@@ -212,6 +216,8 @@
             case .stationary: phase = "S"
             case .ended: phase = "E"
             case .cancelled: phase = "C"
+            case .regionEntered, .regionMoved, .regionExited: phase = ""
+            @unknown default: phase = ""
             }
             
             let x = String(format: "%.02f", view.center.x)

Hello! Can we get a quick update for xcode9/swift4 support?

It looks like all the library needs is 3 auto-correct fixes. I can PR them if you like, but they should be super fast either way.

When I perform pod search TouchVisualizer it shows that the latest version is 3.0.1, but I am still able to use latest version mentioned here with pod "TouchVisualizer", '~>3.0.2'.

I have never created or published a pod before so I'm not sure how to keep the pod info updated, but just a heads-up 👍

In our project we are using a custom keyboard and were having difficult showing touches over it. The issue is that Visualizer always adds the TouchView to the keyWindow, but sometimes other windows are over the keyWindow.

We can fix this for our own purposes to use the topmost (as determined by windowLevel) visible window but were wondering if there was any interest in adding that functionality to the main repo. Happy to submit a PR.

Hello and thanks for this framework,

Is there a Swift 3 branch on its way?

I can't use it with Xcode 8 and Swift 3 beta and Cocoapods... Or couldn't find how to.

Thanks!

Bumps cocoapods-downloader from 1.1.3 to 1.6.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Issue If Visualizer.sharedInstance is not invoked before app is active, calling start function won't work. This is because the swizzling relies on the appBecomeActive notification, and the notification registration is upon initialization of Visualizer.

Fix

• Put the swizzling function in the initialization process of Visualizer.sharedInstance. This guarantees whenever the start is called, we'll always get the function swizzled.
• Remove the unnecessary bool check: As the singleton is guaranteed to be executed once in the application lifecycle, we won't need to worry about the function gets swizzled back.

I have a triple/triple click easter egg I use to toggle this on/off. It's great for making instructional videos. I find that the first time it gets turned on, it won't take until I switch away and back to my app to start seeing this visualization. After that initial swap, it toggles on and off just fine. It's just the first activation that doesn't take without an additional application reactivation.

I have been working on to show the touch visualizer on the video I recorded with ReplayKit but it is not showing any touch at all. What could be the problem?

An NSTimer is not the optimal way to draw stuff to the screen that needs to refresh every frame. CADisplayLink is way better. It always fires immediately prior to the screen being redrawn.