🚀 go-pugleaf

Jason:

You could do it with threads (and handle the interactions, of
course).  I'm only responding because the operations you mentioned are
interesting.  Have you actually tried your Applet in deployed state on
the net?  I ask because some of what you are planning on doing are
forbidden to Applets without jumping through a few flaming hoops.

It's all trivial as an Application.

-Rich

Jason C. Leach wrote:
> 
> hi,
> 
> My applet is coming along nicely. Thanks to this news group.  One think
> I am going to need, I think, is a thread.  Here is what  my app does.
> 
> Opens an input file. (FileChooser, File, and FileInputStream).
> Creates and output file. (FileChooser, File, and FileOutputStream).
> The processes the file when a button is clicked. (Read(), Check(),
> Write()).
> 
> The processing consists of a method that reads in byte, passes to a
> function that checks it, then it is either written to the output file or
> not.  This process makes my Applet (or JFrame) unusable for the duration
> of the processing. Until the file is finished.  I'd like the Applet to
> be more responsive during this time, be able to repaint (if the window
> is covered by another, then uncovered), and a progress bar to be
> updated, o and maybe a cancel button later.
> 
> I am thinking I should put the checking procedure in a Thread.  Does
> this sound like the best way to handle this problem?
> 
> Thanks,
>     Jason
> 
> --
> 
> �,+���+,��,+���+,�*
> ....Jason C. Leach
> ..."Many Hands Make Light Work."
> ..- Unknown
> 
> -- PGP key on server: pgpkeys.mit.edu

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=