Java Tips
When compiling and executing, you will need to include the jigl package in your classpath. Here are some examples:
Compiling:
javac -classpath .;jigl.jar ICEImage\*.java
Executing:
java -classpath .;jigl.jar ICEImage.CameraTest
OR
java -cp .;jigl.jar ICEImage.CameraTest
These examples were done with the D: drive, with all the ICEImage stuff extracted into a directory called D:\ICEImage. The jigl.jar file is placed in D:\, and the two lines above were typed in the Command Prompt at the root of the D: drive. Note that CameraTest.java is a member of the ICEImage package already.
You may also try and change the environment variables so that the jigl jar is included in the classpath. You can do this by
- Right-Click "My Computer" and select "Properties"
- Click the "Advanced" tab.
- Click the "Environment Variables" tab.
- Add or alter the "CLASSPATH" variable to your "User Variables"
- If you already have a CLASSPATH variable, just put this on the end of the string:
;jigl.jar
- Otherwise, if you had to create a CLASSPATH variable, put this in for its value:
.;jigl.jar - notice that this starts with a period
Changing the environment variables may or may not work. I do not know if those values are saved on the CS server for you. I suspect that they are, though, because you can alter them.
It may dump out a bunch of error messages about not being able to set some Registry Keys. Don't worry about it. If you are having other major problems, you may need to have your CS account reset. Check the CS home page for more information.
After you get images from the camera, you may notice a significant slow-down of the camera. This is caused by getting images from the camera, and processing them on the same stack/thread that produced the image. You may want to set something up where the camera constantly updates a variable that holds the latest image, and then a different thread that is doing all the processing just grabs that value. You will have a more responsive camera if you do that.
|