and explains why it worked for Windows. that was all macOS declares
At least we’ll know to ask about declare usage next time 
yeah… 
but even so… the SELF vs ME was a fluke.
The original code I copied that from used SELF… and I just happened to run mouse over it, and realized the IDE said it was the container, not the TextArea
But it also points out the potential danger of Declares… seems some pointer values are “valid”, when in fact they aren’t… and the fact that 64bit said “Shhhhh…lets no say anything”… it was another fluke that I tested in 32bit, and got a vague clue which led to the solution. After Catalina, if 64bit is still silent, then this type of issue will get REALLY had to track
Enter the following in Terminal (replace HDRtist NX with your application name).
log show --predicate 'process contains[cd] "HDRtist NX" && activityIdentifier == 0' --last 8h --style syslogThis will show you the NSException that’s occurring and a stack trace to it, plus lots and lots of other useless ■■■■.
Yes, but the code above will help you in the future.
I see this far more often than I should, but that’s what you get when the OS changes so rapidly with very little care for compatibility.
Thanks Sam
I’ve seen this behaviour for years.
I dont have any container controls on the window.
So on Mac, I use the Activate method to check if the initialisation has been done, and do it there.