On Thu, Mar 17, 2022 at 8:57 PM Philippe Mathieu-Daudé
wrote:
>
> From: Paolo Bonzini
>
> Simplify the initialization dance by running qemu_init() in the main
> thread before the Cocoa event loop starts. The cocoa_display_init()
> code that is post-applicationDidFinishLaunching: moves to the
> a
On Thu, Mar 17, 2022 at 8:57 PM Philippe Mathieu-Daudé
wrote:
>
> From: Paolo Bonzini
>
> Simplify the initialization dance by running qemu_init() in the main
> thread before the Cocoa event loop starts. The cocoa_display_init()
> code that is post-applicationDidFinishLaunching: moves to the
> a
On Thu, 17 Mar 2022 at 11:57, Philippe Mathieu-Daudé
wrote:
>
> From: Paolo Bonzini
>
> Simplify the initialization dance by running qemu_init() in the main
> thread before the Cocoa event loop starts. The cocoa_display_init()
> code that is post-applicationDidFinishLaunching: moves to the
> app
On 17/3/22 12:56, Philippe Mathieu-Daudé wrote:
From: Paolo Bonzini
Simplify the initialization dance by running qemu_init() in the main
thread before the Cocoa event loop starts. The cocoa_display_init()
code that is post-applicationDidFinishLaunching: moves to the
application delegate itself
From: Paolo Bonzini
Simplify the initialization dance by running qemu_init() in the main
thread before the Cocoa event loop starts. The cocoa_display_init()
code that is post-applicationDidFinishLaunching: moves to the
application delegate itself, and the secondary thread only runs
the rest of q