FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 131 : stop() not always called, inconsistencies with start(), stop(), and destroy()
Last modified: 2010-06-05 10:29
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
ASSIGNED
Resolution:
-
Pr
i
ority:
P3
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
fry
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Different browsers start() stop() behavior, comma seperated
text/plain
2010-01-10 13:12
454 bytes
Description
: Opened: 2005-08-14 16:03
stop() not getting called.. and start() is supposedly called by the applet viewer, so it being
called inside paint() is actually ignored.
http://java.sun.com/j2se/1.4.2/docs/api/java/applet/Applet.html#start
()
need to just spend some time sitting and straightening this out. unfortunately requires a lot
of testing between platforms, browsers, and locally inside the pde itself.
Additional Comment
#1 From Lonnen 2010-01-10 13:12
edit
]
Different browsers start() stop() behavior, comma seperated
Compiled a small applet that prints to the error console when start() and
stop() are called, then loaded it in multiple browsers. All OS/browsers were
the latest update prior to testing. JRE was the latest update recommended by
each browser. At the moment Chrome on OSX does not appear to support java
applets. Safari on OSX calls stop when you switch away from the tab and calls
start when you switch back to the tab containing the applet. Otherwise all
other tested browsers on all platforms followed the same pattern -- call
start() when created, do nothing when switching tabs, and call stop() when the
applets tab is closed.
Browsers tested
OSX: Chrome, Firefox, Safari
Ubuntu: Chrome, Firefox, Opera
XP: Chrome, Firefox, IE7, IE8, Safari
Additional Comment
#2 From fry 2010-06-05 09:25
***
Bug 183
has been marked as a duplicate of this bug. ***
Additional Comment
#3 From fry 2010-06-05 10:29
***
Bug 77
has been marked as a duplicate of this bug. ***