PulpCore App Stuck When Refreshing Browser

[Ido Yehieli]

Hi,
the pulpcore game I am developing (can be seen http://tametick.com/test/)
seems to work fine when first loaded, but when you refresh the browser
it seems to get 'stuck' (load the url, refresh the page & click
anywhere on the applet window).

Any idea what is causing it? Doesn't seem like any exception
stacktrace is printed in the java console.

Source can be seen at:
http://code.google.com/p/cardinal-quest/source/browse/trunk

Thanks,
Ido.

[Dori]

Hi, im getting the following trace from the console

Reading certificates from 11 http://tametick.com/test/CardinalQuest.jar
| C:\Documents and Settings\Dori\Application Data\Sun\Java\Deployment
\cache\6.0\53\6e4c55f5-5b377fc6.idx
PulpCore 0.11.5 (2009/04/15 07:04:17)
APPLET tag missing CODE parameter.
java.lang.IllegalArgumentException: n must be positive
at java.util.Random.nextInt(Unknown Source)
at ad.b(Unknown Source)
at ad.a(Unknown Source)
at client.CardinalQuest.a(Unknown Source)
at as.l(Unknown Source)
at as.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

hope that helps! im imagine your a better java programmer than me, i
remember running into a problem when i was setting a static flag when
loading an applet, not noticing that the static variables were
persisting through page/applet reloads (until clearing the cache)
which caused me problems. Looks like you maybe passing a negative int
into the nextInt method?

Dor

On Sep 16, 10:46 am, Ido Yehieli <ido.yehi...@gmail.com> wrote:
> Hi,

> the pulpcore game I am developing (can be seenhttp://tametick.com/test/)

[Dori]

looks good though!

On Sep 16, 10:46 am, Ido Yehieli <ido.yehi...@gmail.com> wrote:

> Hi,
> the pulpcore game I am developing (can be seenhttp://tametick.com/test/)

[Ido Yehieli]

The nextInt(...) thing is ok, I am catching that exception and
handling it (just printing to the console).

I think the problem might be with the static fields, I didn't know
they were persisting through page/applet reloads.

Thanks,
Ido.

[Dorian Cussen]

i cant remember the exact details of my problem, but it's worth checking...

2009/9/16 Ido Yehieli <ido.y...@gmail.com>

[David Brackeen]

It looks like the applet was built in 'release' mode. It would be easier to tell what was happening in 'debug' mode.

[Ido Yehieli]

You are right, sorry about that.

I rebuilt in debug mode and put it on tametick.com/test/ again, seems
like i am getting a NullPointerException when I refresh the browser...

Thanks for your help,
Ido.

On Sep 16, 5:26 pm, David Brackeen <brack...@gmail.com> wrote:
> It looks like the applet was built in 'release' mode. It would be easier to
> tell what was happening in 'debug' mode.

> On Wed, Sep 16, 2009 at 3:11 AM, Dorian Cussen <dorian.cus...@googlemail.com

>
> > wrote:
> > i cant remember the exact details of my problem, but it's worth checking...
>

> > 2009/9/16 Ido Yehieli <ido.yehi...@gmail.com>