> On Mar 18, 2023, at 4:46 AM, Michael Hall <[email protected]> wrote:
>
> The main differences seeming to be that it takes a pass through the CFRunLoop
> doing an invokeBlockCopy
After seeing this (java_md_macosx.m JVMInit sameThread is true)…
/*
* We cannot use dispatch_sync here, because it blocks the main
dispatch queue.
* Using the main NSRunLoop allows the dispatch queue to run
properly once
* SWT (or whatever toolkit this is needed for) kicks off it's own
NSRunLoop
* and starts running.
*/
I would think the problem is that -XrunOnFirstThread is intended for ’toolkit’s
that aren’t Swing based but handle the gui and NSRunLoop as indicated
themselves - like Eclipse with SWT.
Arbitrary Swing app’s just can’t use this jvm switch.
Sound plausible?
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
