Angelo Sarto a icrit :

All,

I hope james will correct me if I'm wrong but are you tring to
serve the applet from one IP and connect to another?


Actually, I do not use the Java client as an applet. In one case, I use it as a standalone application (running 'java -jar vncviewer.jar' which calls VNCViewer.main()). In the other, I create an instance of the VNCViewer class and call 'start()' on it.

Because it isn't signed you cant violate the sandbox of java (thanks
for making me relize this James)

You could try signing your module and possibly this would make it
accessible.  Although if your module loads another module I don't know
how trust issues work in Java.

--Angelo



I think these problems occur only in the case of a web hosted applet. What I do is ship the vncviewer.jar file as a library to my NB module and just open the applet in standalone mode from another class.

Could it possibly be a Thread concurency problem ? I.e another thread grabbing the keyboard input instead of the PasswordDialog ? I was thinking about recoding the whole thing using Swing instead of AWT.

Please help, this is a crucial point of my app... Thanks and regards,
-JBL
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to