FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 539 : Processing cancels shutdown on Mac OS X
Last modified: 2008-10-21 10:26
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P5
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
fjen
Assigned To:
fry
Attachment
Type
Created
Size
Actions
finder message: shutdown-process cancled
image/png
2007-04-02 01:57
19.01 KB
Description
: Opened: 2007-04-02 01:56
when you shut-down your system from the finder ( or via power-button ) and the process then
tries to quit processing it's cancled even if there are no modified tabs.
really a minor non-important bug, but i thought i'd report it nonetheless.
Additional Comment
#1 From fjen 2007-04-02 01:57
edit
]
finder message: shutdown-process cancled
Additional Comment
#2 From fry 2007-04-02 05:22
this happens all the time? no matter what? processing will always cancel
shutdown? i'm surprised that i've never seen this before.
Additional Comment
#3 From fjen 2007-04-02 05:33
yep. allways. no sketch running. to test: just open processing and press the powerbutton,
choose shutdown and there you go ..
Additional Comment
#4 From fry 2007-04-02 07:44
confirmed. my guess is that it's because we use the Java 1.3 version
(com.apple.mrj) of apple's event handling methods, and need to update to
1.4 (com.apple.eawt).
processing in fact quits, it's just that the shutdown is interrupted.
i wonder if it just doesn't quit quickly enough or doesn't pass some sort
of message. this kind of thing is usually buried in some apple technote...
Additional Comment
#5 From fry 2008-10-21 09:42
Is this still a problem in more recent releases?
Additional Comment
#6 From fjen 2008-10-21 10:25
nope, seems fixed.
java 1.5.x
processing 0152
Additional Comment
#7 From fry 2008-10-21 10:26
Good, I think it went away when I did the newer platform stuff a while
back, and I just didn't close the bug. Thanks for checking.