> On Mar 19, 2023, at 10:37 AM, Alex Zavatone <z...@mac.com> wrote: > > So while I am waiting for my coffee to actually start working, which > approaches do we think make sense here? > > When starting up, check if thread == main and if so, do one thing, else do > the other? > > If this is correct, what would each option be? > > Is this an appropriate summary or a vast oversimplification? > > Cheers, > Alex Zavatone > > Sent from my iPhone >
I think I’ve put about as much time into this as I mean to right now. But, what I think I’ve sort of concluded from what I saw in NSLog tracing the startup and what I’ve seen or heard in the past. The java Swing (GUI) normally starts up and manages it’s own threads and run loop. The Eclipse IDE came up with its own GUI called SWT, don’t know what that stands for, something windows toolkit probably. Pretty much just for that a -XstartOnFirstThread option was added that runs on the Cocoa main thread. However, it appears some of the run loop handling Swing normally does is up to the responsibility of applications using that launch switch. So use the switch for Swing applications and the normal setup isn’t done and Swing hangs. Bug Report. But probably not going to be fixed because the switch was never intended to be used for Swing applications. Not worth too much more looking at I don’t think once I saw the comment that applications using the switch were on their own for managing run loops. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
