T
tom baker
Hi there,
I'm programming an application for touchscreens. Each 'page' on the
screen is a JFrame. Among other criterions it's IMHO the easiest way
to go into 'idle'-state (by using a javax-Timer with 'dispose').
Each new JFrame (e.g. ttt= new gui_menu_one(); ) creates a new linux
thread (or process). But after dispose() the thread/process of this
JFrame is still there. Now I worry about that the whole system could
slow down or stop after a certain time, because the OS still has to
provide ressources for these non-active processes/threads.
What is the cause? java?
Is it right, that a dispose releases all resources (including the
threads) ?
I'm using SuSE Linux 8.1 with Sun Java 1.4.2_05
Thanks for your assistance !!
Pseudocode:
public class gui_initialstart extends JFrame
// Constructor
// Actionlistener:
// Call Menu 1:
ttt= new gui_menu_one();
// Call Menu 2:
public class gui_menu_one extends JFrame
// Constructor
// Actionlistener
// write into file and dispose()
I'm programming an application for touchscreens. Each 'page' on the
screen is a JFrame. Among other criterions it's IMHO the easiest way
to go into 'idle'-state (by using a javax-Timer with 'dispose').
Each new JFrame (e.g. ttt= new gui_menu_one(); ) creates a new linux
thread (or process). But after dispose() the thread/process of this
JFrame is still there. Now I worry about that the whole system could
slow down or stop after a certain time, because the OS still has to
provide ressources for these non-active processes/threads.
What is the cause? java?
Is it right, that a dispose releases all resources (including the
threads) ?
I'm using SuSE Linux 8.1 with Sun Java 1.4.2_05
Thanks for your assistance !!
Pseudocode:
public class gui_initialstart extends JFrame
// Constructor
// Actionlistener:
// Call Menu 1:
ttt= new gui_menu_one();
// Call Menu 2:
public class gui_menu_one extends JFrame
// Constructor
// Actionlistener
// write into file and dispose()