" Why are you compiling a plugin for 32 bits?" Because plug-ins must match
the host app. In this case the host app's 64 bit version was only released
4 years ago. (The host app is made by a third party).
Older versions of the app run on 10.14 and are still widely used by our
customers. So, while
> 2019. 10. 19. 오전 9:17, Alex Zavatone via Cocoa-dev
> 작성:
>
> Wow was this ever fun.
>
> Woo hoo!
>
> Let this be an exercise in the dangers of memory leaks.
>
> Our team uses VIPER with everything being strongly linked. Also in
> Objective-C, there are cases where private instance
Hello Cocoa List,
I’m in the process of porting a hobby project to up-to-date Swift so it can be
used on Catalina (and I can upgrade my work machine - still looking for a
QuickTime 7 Pro replacement, though). I’ve encountered a phenomenon
subclassing NSCollectionViewFlowLayout that I haven’t
Your email client line breaking makes for very difficult reading so I
reformatted. See below.
Why are you compiling a plugin for 32 bits?
Just tested a 64 bit app linked to 10.8 and an unhandled rightMouseDown is
passed promptly from view to window. Testing in 32 bits would be a lot of work.
