suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cocoa: change the way the app is initialied

Browse Source 
Calling NSApplication's `run' works better than calling `finishLaunching'
directly, particularly in 64-bit Lion for some reason.

Relevant to PR 12102
Relevant to PR 12257
This commit is contained in:
Matthew Flatt 2011-10-07 07:51:28 -06:00
parent 94a9a808ec
commit 60101618db
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
collects/mred/private/wx/cocoa/queue.rkt
View File

@ -78,7 +78,8 @@
(queue-file-event (string->path filename))]
[-a _void (applicationDidFinishLaunching: [_id notification])
(unless got-file?
(queue-start-empty-event))]
(queue-start-empty-event))
(tellv app stop: self)]
[-a _BOOL (applicationShouldHandleReopen: [_id app] hasVisibleWindows: [_BOOL has-visible?])
;; If we have any visible windows, return #t to do the default thing.
;; Otherwise return #f, because we don't want any invisible windows resurrected.
@ -132,7 +133,11 @@
(unless (zero? v)
(log-error (format "error from CGDisplayRegisterReconfigurationCallback: ~a" v))))
(tellv app finishLaunching)
;; To make sure that `finishLaunching' is called, call `run'
;; and have `applicationDidFinishLaunching' quit the run loop,
;; which seems to work better than calling `finishLaunching'
;; directly.
(tellv app run)
;; ------------------------------------------------------------
;; Create an event to post when MzScheme has been sleeping but is