Windows 95 can be locked up when running the debugger.
1. launch the debugger and wait for all the windows to appear
2. using the *right* mouse button, activate the pulldown menu on the windows 95 "taskbar" usually located at the bottom of the screen.
3. from the pulldown menu, select "minimize all".
Problem:
If the debugger is running, the applet viewer window should also be present and waiting to display the applet for debugging. However, until the applet is stepped through, the user CANNOT move, close, or MINIMIZE the applet viewer. At this point if the user tries to minimize all the windows, the entire windowing system will freeze up as it will be waiting for the applet viewer to minimize.
The only way to continue is to kill the applet viewer (ctrl-alt-del works sometimes). However, if the user does this, the current JWS session cannot continue.
Scott
-------------------------------------------------------------
I tried this out in JWS 2.0 beta and it still exist. It still looks
like an AWT bug. Should we be getting a "minimize all" message that
we are not receiving? I'll recategorize it. Maybe the awt group
will have some insight.
vincent.henry@Eng 1997-07-14
1. launch the debugger and wait for all the windows to appear
2. using the *right* mouse button, activate the pulldown menu on the windows 95 "taskbar" usually located at the bottom of the screen.
3. from the pulldown menu, select "minimize all".
Problem:
If the debugger is running, the applet viewer window should also be present and waiting to display the applet for debugging. However, until the applet is stepped through, the user CANNOT move, close, or MINIMIZE the applet viewer. At this point if the user tries to minimize all the windows, the entire windowing system will freeze up as it will be waiting for the applet viewer to minimize.
The only way to continue is to kill the applet viewer (ctrl-alt-del works sometimes). However, if the user does this, the current JWS session cannot continue.
Scott
-------------------------------------------------------------
I tried this out in JWS 2.0 beta and it still exist. It still looks
like an AWT bug. Should we be getting a "minimize all" message that
we are not receiving? I'll recategorize it. Maybe the awt group
will have some insight.
vincent.henry@Eng 1997-07-14