On 03/06/07, Anthony Fairchild <[EMAIL PROTECTED]> wrote: > Hello everyone, > > I think I found 2 problems with cocoahelper. The first is the asdf system > name did not match the name of the .asd file, this was causing problems when > trying to 'load-op: <SNIP> > Now with those changes, I'm still having trouble getting my game to work. I > can get the game window to show, but mouse clicks and key presses do not > work. Regarding cocoahelper, the website states: > > "This creates an instance of NSApplication that serves as a bridge between > SDL and Cocoa, similiar to that used by the Python project Pygame. If this > is successful, you should see the icon for a generic OS-X ap appear in your > dock." > > But I dont see an OS-X app in the doc after cocoahelper is loaded. > > I'm using Lispworks Pro 5.0.2 on an Intel Mac with the latest OS patches. > > Anyone have a clue about this one? > > Thanks! > > AnthonyF
I've recently just run into this problem. I'm the original author of cocoahelper, and I bascially copied from what Python does. I happen to be running multithreaded SBCL + Slime. I think that the problems you are having are due to Cocoa and the way that OS X handles events. All events are sent to the main thread. I basically gave up & used GLFW to open up my window (I only care about an OpenGL window and events right now). GLFW is Carbon based, and suffers less issues - but I still couldn't run my Slime multithreaded. I'm afraid that it will probably take somebody with a bit of time/effort/Cocoa experience to sort this one out. Cheers Brad _______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
