I don't know what you mean by unresponsive. I hope you don't mean that the window would be dimmed and have the appearance of being locked up and appear crashed, without the ability to copy and past from it, or to resize it. If that is what you're saying, it would be horrible. Some of my current experiments has had the effect of what I just described. Something like that would be totally unacceptable.
I hope the window will always appear normal just like any window. I'll look at the link you gave and see if I can find something to incorporate in the test I'm already doing. I don't know if Alan has worked out the bugs. But I described how this is done in the other GUI environments in which I've works. I elaborated on how it's done in Java. He said Gtkmm has the same functionality. I'm glad that others are looking at this problem and simultaneously trying to figure out how to work things out. By the way, I'm not a good enough program to know where the thread/operation goes when the code is sitting waiting for a button to be clicked. Also, I wouldn't want to edit any of that code (I wouldn't think of it). But is seems logically to be able to have some type of routine where the processing goes into your code instead of the button code, and you communicate with the buffer that is in the Window. The window isn't "non responsive" when it's in the "button" code (or whatever you call cycling through that function waiting for input). While it's there it doesn't appear dim or locked up. You can copy text from the content, resize it, or click on the window x to close the window. If such a description wouldn't be possible, the gui functionality would be unacceptable. I find it incredible that no one (except most likely Alan) can figure out an easy way to send a line of text to a window, then perform some program functions, then without user input send another line of text to the window. Such functionality appears to be so basic. There's a chance that the many people that are trying to figure this out are actually missing the essence of what I'm describing. I might be making it sound like something complicated, so I might be throwing some people off. That is the reason I try to find more ways to describe it. I'm sure many people have code that is doing exactly this. They just are not thinking about it. There has to be a simple way to append text to text already displayed without the user having to sit at the console and click a button every time they want the program to continue. I'll comment again after I have studied the link you provided. Thanks! -- L. James -- L. D. James lja...@apollo3.com www.apollo3.com/~ljames On Fri, 2013-08-02 at 10:25 +0200, Murray Cumming wrote: > OK, if you don't care about making the window unresponsive while > processing is happening then this example should be helpful: > https://git.gnome.org/browse/gtkmm-documentation/tree/examples/book/idle > > You should worry about making the window unresponsive, regardless of the > programming language, but it seems like you need to start with something > simpler. >
_______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
