My favorites | Sign in
Project Home Downloads Issues
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 2: On OSX, need to force quit the process
2 people starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  thomas.h...@gmail.com
Closed:  Jan 2009


 
Project Member Reported by leca...@gmail.com, Nov 19, 2008
Under OSX with Python 2.6, I can close pymt windows by pressing escape, but
it doesn't kill the process.  Afterwards, I can't seem to kill the process
in the terminal with ctrl-x or ctrl-c, I need to manually kill it with the
PID, any ideas why this is happening ?

Thanks,

Nat
Nov 19, 2008
Project Member #1 thomas.h...@gmail.com
I have noticed this as well.  I'll take a look at it, it might be a simple fix in 
attaching an function calling sys.exit() to the window close handler.  Not sure why 
it behaves differently only on OSX, might be a pyglet issue.
Nov 25, 2008
Project Member #2 felipe.c...@gmail.com
I guess that is because the settimout() line that had been commented ... the sockets 
still work after closed the window!
Dec 14, 2008
Project Member #3 thomas.h...@gmail.com
still seems to be an issue.  I think Felipe is right, it has to do with the osc 
connection.  will need to take a closer look at this soon.  (after finals :P)
Status: Accepted
Owner: thomas.hansen
Labels: -Priority-Medium Priority-High
Dec 14, 2008
Project Member #4 thomas.h...@gmail.com
(No comment was entered for this change.)
Labels: OpSys-OSX
Dec 29, 2008
Project Member #5 txprog
I've the same issue in ubuntu intrepid with latest svn version.
Jan 6, 2009
Project Member #6 txprog
This is the commented settimeout line.
We got 2 solutions: 
- use no-blocking socket
- repair issue with MTSimulator(?) and timeout socket
Jan 6, 2009
Project Member #7 txprog
I've remove the timeout. Please fill a bug report if MTSimulator don't work !
(commited as r61)
Status: Done

Powered by Google Project Hosting