RE: JTOpen ProgramCall doesn't work

I framed it that way because, until Java 1.4, the AWT threads never ended
anyway so it didn't matter what you did with the Dialog when you were done
with it. Now, they do end but it is really a philosophical question as to
whether you should do the extra work to end them or just ask the user to
signal when he or she is done by using System.exit(). I didn't want to step
on their toes if they'd already had that philosophical discussion.

Gary

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Friday, May 02, 2008 10:43 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: JTOpen ProgramCall doesn't work

Gary L Peskin wrote:

Should the actionPerformed method instead call Dialog.dispose or at

least

set displayable to false or something to cause the non-daemon threads

to

end?

You framed it as a QUESTION?!?

At any rate, you got their attention, and hopefully, it might actually
get fixed.

And once again, thanks for all the help yesterday. I've passed my test
program on to a colleague who will see if it can be made to work on the
box that's the real target for the whole project.

--
James H. H. Lampert
Touchtone Corporation

--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.