 |
AppletTalk.com Java discussions newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
hiwa Guest
|
Posted: Wed Jan 19, 2005 11:40 pm Post subject: Problem with JPopupMenu (I think...) |
|
|
One of the top five worst practices for GUI programming:
-Instantiating a component in an event listener.
It also belongs to the top five never-do-it practices for GUI programming.
BTW, is accessing client's System.out in an applet legal? I'm
not so sure about it.
|
|
| Back to top |
|
 |
Andrew Thompson Guest
|
|
| Back to top |
|
 |
blue Guest
|
Posted: Thu Jan 20, 2005 3:07 pm Post subject: Re: Problem with JPopupMenu (I think...) |
|
|
I tried changing the code so that no components are instantiated in the
event listeners, this did not help.
Thanks for the insight? though.
Frank
"hiwa" <HGA03630 (AT) nifty (DOT) ne.jp> wrote
| Quote: | One of the top five worst practices for GUI programming:
-Instantiating a component in an event listener.
It also belongs to the top five never-do-it practices for GUI programming.
BTW, is accessing client's System.out in an applet legal? I'm
not so sure about it.
|
|
|
| Back to top |
|
 |
RC Guest
|
Posted: Thu Jan 20, 2005 9:54 pm Post subject: Re: Problem with JPopupMenu (I think...) |
|
|
All System.out will go to Java console for Applets.
"blue" <fluyckx (AT) configsc (DOT) com> wrote
| Quote: | I tried changing the code so that no components are instantiated in the
event listeners, this did not help.
Thanks for the insight? though.
Frank
"hiwa" <HGA03630 (AT) nifty (DOT) ne.jp> wrote in message
news:6869384d.0501191540.3b81448c (AT) posting (DOT) google.com...
One of the top five worst practices for GUI programming:
-Instantiating a component in an event listener.
It also belongs to the top five never-do-it practices for GUI
programming.
BTW, is accessing client's System.out in an applet legal? I'm
not so sure about it.
|
|
|
| Back to top |
|
 |
Roland Guest
|
Posted: Fri Jan 21, 2005 11:02 am Post subject: Re: Problem with JPopupMenu (I think...) |
|
|
On 20-1-2005 9:54, Andrew Thompson wrote:
I think that needs some further clarification.
In an unsigned applet you *can* print to System.out/System.err (using
System.out.println(), System.err.print(foo) etc.). The output will show
up in the Java console.
But you cannot change System.out/System.err to your own PrintStream.
Calling System.setOut(PrintStream) or System.setErr(PrintStream) in an
unsigned applet (with default security permissions) will throw a
security exception.
--
Regards,
Roland de Ruiter
___ ___
/__/ w_/ /__/
/ /_/ /
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|