Re: Future of Cocoa

Now that I think about it, you can probably do this without support from the runtime by interposing the handful of runtime functions that invalidate the method cache… Saagar Jha > On Dec 16, 2019, at 00:23, Jean-Daniel wrote: > > My bad, I just see that when rereading the description. Of cour

Re: Catalina scroll view issues

If you’re not involving a higher level class like NSTextView or a medium level one like CoreText, it sounds like you might be going all the way down to CoreGraphics? If so, you might find your disparity between your system and your users in things like retina choice for a particular display and

Re: Catalina scroll view issues

Thanks Rob, Makes sense although the issue is not consistent on Catalina (I think this is something only a minority of my app users on Catalina are experiencing - and I wasn't able to reproduce it). I saw this deprecation but could not be sure if it means that it is always on or always off. I gu

Re: Catalina scroll view issues

Thanks! I don't use CoreText or NSTextView. I pretty much ruled out RTL vs LTR issues since this is showing up in documents containing either and both. I'm also unable to imagine how some text drawing code could produce such artifacts as splitting a subview in the middle. (http://eyalredler.com/

Re: Future of Cocoa

My bad, I just see that when rereading the description. Of course, it will requires an updated runtime. > Le 16 déc. 2019 à 09:21, Saagar Jha a écrit : > > There’s also a check for method swizzling and other invalidation, assuming > that there is cooperation from the runtime. Unless I’m misund

Re: Future of Cocoa

There’s also a check for method swizzling and other invalidation, assuming that there is cooperation from the runtime. Unless I’m misunderstanding what you mean by the selector changing? Saagar Jha > On Dec 16, 2019, at 00:16, Jean-Daniel wrote: > > >> Le 16 déc. 2019 à 06:05, Saagar Jha > <

Re: Future of Cocoa

> Le 16 déc. 2019 à 06:05, Saagar Jha a écrit : > > It’s been a while, but I just thought you both might be interested in some > follow-up I did for this idea. I implemented it for fun in clang > and it turns out that it’s a > pretty decent performan