listen for
input on stdin (i.e., when the user types in the next Python command at the
Python prompt), and I want to stop the event loop if such input is available.
Then I let Python execute the command, and I restart Cocoa's event loop once
Python is done. Works beautifully, except
On Oct 9, 2008, at 20:47 , Michiel de Hoon wrote:
--- On Thu, 10/9/08, Jason Coco <[EMAIL PROTECTED]> wrote:
Submit a bug report and use a CFRunLoop for now :)
In my understanding, CFRunLoop cannot replace [NSApp run] for GUI
applications. For example, see this thread:
http://lists.apple.
On Thu, Oct 9, 2008 at 9:15 AM, Michiel de Hoon <[EMAIL PROTECTED]> wrote:
> Hi everybody,
>
> According to the documentation, [NSApp stop:] will break the flow of control
> out of the [NSApp run] method. While this is true, [NSApp run] doesn't
> notice that [NSApp st
--- On Thu, 10/9/08, Jason Coco <[EMAIL PROTECTED]> wrote:
> Submit a bug report and use a CFRunLoop for now :)
>
In my understanding, CFRunLoop cannot replace [NSApp run] for GUI applications.
For example, see this thread:
http://lists.apple.com/archives/Cocoa-dev/2008/Mar/msg01372.html
So I g
On Oct 9, 2008, at 09:15 , Michiel de Hoon wrote:
Hi everybody,
According to the documentation, [NSApp stop:] will break the flow of
control out of the [NSApp run] method. While this is true, [NSApp
run] doesn't notice that [NSApp stop:] was called until some other
event comes
Hi everybody,
According to the documentation, [NSApp stop:] will break the flow of control
out of the [NSApp run] method. While this is true, [NSApp run] doesn't notice
that [NSApp stop:] was called until some other event comes along. So I call
[NSApp stop:], nothing happens, and when I
