// Thread 2
// Do blah blah blah
// Open dialog Box with parent obj as Gtk::Window window;
Gtk::MessageDialog dialog(*pWindow, "blah");
dialog.run(); // SIGABRT happens sometimes but sometimes it dosent
// sleep or exit when condition satisfies
// Thread 1
// create a thread for someobj.run()
// start window
//Join thread for some object.run()
I think it is not dependent on gtkmm because thread 2 is blocked where as the parent thread is running which is causing the problem, but am confused on how to resolve this... any suggestion will be helpful
yes i agree a dialog running independent of GUI doesnt make sense,
but my problem is a little different...
suppose say the main thread is for the gui and a child thread is monitoring some other resource, say a website, when that website is available the child thread needs to display a yes/no message box to ask the user something...
so how would this normally work??