Ok it seems `initialize-ns-app' might not be necessary after all, sorry. I
looked at the python allegro5 bindings and they run a users thunk by passing it
to al_run_main which does all the proper initialization.
;; allegro5.rkt
(define (run thunk)
(define (callback argc argv)
(thunk)
0
On Sunday, January 13, 2013, Jon Rafkind wrote:
> Does the entire application have to live within the dynamic extent of the
> `initialize-ns-app' call or just making the screen?
>
>
I have not tested this, but I think it may be sufficient to wait until the
system calls activateNow. So maybe add a
Does the entire application have to live within the dynamic extent of the
`initialize-ns-app' call or just making the screen?
(initialize-ns-app (lambda () (create-display))
(do-rest-of-program)
or
(initialize-ns-app (lambda () (create-display) (do-rest-of-program))
On 01/13/2013 03:14 PM, Dan
Hi Jon,
[Also CCing the Racket mailing list. For folks who are writing
bindings to graphical libraries such as SDL, the following should be
relevant.]
When using the Allegro bindings on Mac OS X, the user will see an
exception on screen instantiation unless the program's running under a
Cocoa
4 matches
Mail list logo
