It seems that the event-parity layer across AppKit and UIKit (that I just spent a week refactoring into my vector canvas engine) is somewhat superfluous on Golden Gate.
But alas I am supporting back to MacOS 15, so it was still worth writing it!
It seems that the event-parity layer across AppKit and UIKit (that I just spent a week refactoring into my vector canvas engine) is somewhat superfluous on Golden Gate.
But alas I am supporting back to MacOS 15, so it was still worth writing it!
@amyworrall Oh, what do you mean by event-parity layer?
@Cykelero My vector engine was originally Mac-only, and pretty much forwarded AppKit’s mouse event messages to a different ‘handler’ depending on tool and mode. I recently brought it to iPad, and suddenly I had to distinguish touches, multi-touch gestures, Apple Pencil events, etc… so I built a wrapper that I could populate from the AppKit handlers or from UIKit gesture recognisers, then pass one type around my cross platform code.
@amyworrall Ooh, I see, cool stuff! And now if you targeted 27 only, you could replace that wrapper with a thin translation layer, that would only deal with the much smaller differences with the touch APIs on iOS, and the new touch APIs on macOS.