However, Apple is also designing iPhone 16 versions without Capture buttons in case the project fails. Moreover, it’ll be available on eSIM-only and SIM models. The report says the Capture button will be available on all four iPhone 16 models. The blog cites “unsatisfactory test results and a significant number of hardware issues” as the reasons for the cancellation. However, Apple had to cancel the project early during development. It also wanted to turn the power button into a capacitive button. Apple wanted to replace the volume rockers with a single capacitive button. MacRumors previously detailed Apple’s purported “Project Bongo” for the iPhone 15 Pro series. Hope this is helpful! Looks like an interesting automation project.IPhone 15 Pro and 15 Pro Max: Camera systems. Otherwise it sounds like you've found a way to log as well. To do that, I used my TouchRecorder plus TouchExtractor stuff also in that repository (which is very 'works on my machine' with hardcoded paths and junk) but might help. The exact patterns changed a bit (there's a new kTLInfoKeyGesturePhase key in now) and so you may need to take a look at what a real MBP trackpad sends on newer releases. where a dictionary of different keys is sent to a helper for conversion to CGEvent 'fields'. What should still work is the higher-level gesture stuff. These structures do change across OS releases iirc, and also trying to inject them seemed not to work anymore on recent releases when I briefly tested. corresponding to the NSTouch objects an app might also receive. The IOHID stuff you might have seen in my calftrail/Touch code is primarily for sending the actual touches, i.e. Sounds like is on the right track, although I don't think the IOHID structures are particularly relevant. Yes, it is still possible to inject generated gestures as of Sierra (and presumably High Sierra but I haven't tested). So to do this, we'd need to open the popup menu first then slide the slider based on the mouse scrolling, which may or may not Thanks for the mention. Annoyingly, although there is a 'zoom' slider in the Final Cut Pro interface - it's not visible all the time, and is only accessible if you click a button (which pops up a sub-menu). We've currently solving this particular issue by triggering a menu item that does the zooming for us, which works fine on mice with mechanical scroll wheels - but it's really glitchy if you have a mouse with a touch interface (such as Apple's newer mice). Yeah, we use hs._asm.axuielement for a HUGE amount of our GUI Scripting - it's awesome. Not sure if you saw my links in #322, but is Sesamouse relevant? Using this approach takes a lot of trial and error, but I have occasionally found that it provides controllable actions that are difficult or impossible any other way. (see if you want to check out this experimental approach). You could also look into hs._asm.axuielement to see if an accessibility action has been defined for the action you're interested in - specifically look at the actions defined for the target (window, control, etc). Of course this relies on the application actually following those guidelines :-) keyboard shortcut or regular mouse movement), I would see Hammerspoon can perform the action this way.

Since Apple's design guidelines specify that every action that can be performed by a gesture should also be doable through another method (i.e. Hammerspoon) due to restrictions of the NSEvent framework. And even if we could, since they are defined through the NSEvent framework rather than the CoreGraphics event framework, I don't think we could target them at applications other than our own (i.e.

I am not aware of a method to generate gesture events programmatically.

Hammerspoon capture event