🚀 go-pugleaf

In article <370C717A.34D86808@ifi.ntnu.no>, hildepilde@ifi.ntnu.no 
says...
> Yes, I did. Otherwise I would not write this question one more time...
> 

OK, you would be surprised how many folk post accidental duplicates or 
don't read replies before they post again.

I looked back in the thread and I see you've told us that JPassword fails 
in an applet.  Please try to give us a little more detail to work with.  
It will help if you can explain more detail about how it fails (what 
happens/ doesn't happen/ should happen) and if there is an error message 
please quote the text of the message.  If you get a non-english error 
feel free to post the native version and your best guess translation.

FWIW I just tried JPassword in a very quick and dirty applet - it seems 
to work OK in AppletViewer and failed to locate Swing when I tested with  
Netscape.  I didn't have time to follow it more during my working hours,   
Could you have a similar failure, maybe not deploying all the required 
classes and support? 

It might help to isolate the problem if you create the smallest possible 
stand-alone applet which demonstrates the problem.  In this case I would 
suggest something like an applet with two objects - JPassword, and a 
simple text field which echoes the typed characters.  This should 
eliminate most potential interference and reduces the risk of coding 
errors, then add trace code to help you follow events at runtime.  Even 
making it 'beep' (0x7 character) at strategic points in the startup might 
help.


-- 
pf