Sorry, I misread the bug.
You could try catching the null pointer exception that will be thrown from not having an applet, and then displaying whatever help you want.
I actually would say that perhaps an application version of EBJava should be a seperate thing from the applet version, as an application version could do things like download. There would be room for definite branching there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I\'ll fix it tonight. It just opened an webpage in the browser, like AOL\'s Quickbuddy does.
Should be fixed.
Since EB is the class that extends Applet, getAppletContext had to be called on EB, which was root before EBController.
There is a layout problem now that wouldn\'t even let me get to the button to test it, but it should work.
Sorry, I misread the bug.
You could try catching the null pointer exception that will be thrown from not having an applet, and then displaying whatever help you want.
I actually would say that perhaps an application version of EBJava should be a seperate thing from the applet version, as an application version could do things like download. There would be room for definite branching there.
Now it should work for applet, but app does nothing.