I am trying to open a new window after closing the last one, for example like this:
import jcurses.widgets.*;
public class CursesTest
{
public static void main(String[] args)
{
Window w = new Window(40, 20, true, "A Window");
w.show();
w.close();
Window w2 = new Window(50, 20, true, "Another Window");
w2.close();
}
}
When executing this class the following exception is thrown:
Exception in thread "main" java.lang.IllegalThreadStateException
at java.lang.Thread.start(Native Method)
at jcurses.widgets.WindowManager.startInputThread(WindowManager.java:247)
at jcurses.widgets.WindowManager.init(WindowManager.java:231)
at jcurses.widgets.WindowManager.createWindow(WindowManager.java:56)
at jcurses.widgets.Window.<init>(Window.java:78)
at jcurses.widgets.Window.<init>(Window.java:90)
at CursesTest.main(CursesTest.java:10)
This happens with Suns jdk 1.3.1_07, 1.4.0_03 and 1.4.1 and jcurses 0.95. I am using Linux.
Am I doing something wrong or is there a bug?
Thanks
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to open a new window after closing the last one, for example like this:
import jcurses.widgets.*;
public class CursesTest
{
public static void main(String[] args)
{
Window w = new Window(40, 20, true, "A Window");
w.show();
w.close();
Window w2 = new Window(50, 20, true, "Another Window");
w2.close();
}
}
When executing this class the following exception is thrown:
Exception in thread "main" java.lang.IllegalThreadStateException
at java.lang.Thread.start(Native Method)
at jcurses.widgets.WindowManager.startInputThread(WindowManager.java:247)
at jcurses.widgets.WindowManager.init(WindowManager.java:231)
at jcurses.widgets.WindowManager.createWindow(WindowManager.java:56)
at jcurses.widgets.Window.<init>(Window.java:78)
at jcurses.widgets.Window.<init>(Window.java:90)
at CursesTest.main(CursesTest.java:10)
This happens with Suns jdk 1.3.1_07, 1.4.0_03 and 1.4.1 and jcurses 0.95. I am using Linux.
Am I doing something wrong or is there a bug?
Thanks
Robert
I think I have found the reason for this behaviour now. I have reported it as bug with request id 691876.
Regards
Robert