Gtkmm updating gui

Kjell has taken my question serious enough to start an addition to the examples list (multi-treaded example).I've been studying the 400 lines and 11 widget in the example for the past 2 days spending about 6 hours a day going over all the lines and referencing the documentation. When I try to eliminate the unwanted widgets, because of the many lines, my example gets broken and fail to work.I would like to apologize to the community for being so new and using so many words to explain my problem. The minimum amount of lines to use a Text View: //========== Example 1 Begin ============// #include Thanks you plenty, Andrew for giving so much consideration to my question.But if I use a minimum amount of words, someone might spend hours trying to help, but might come up with something that doesn't address the problem. I'm really grateful for the generous comments and white spaces for clarity.Nonetheless, I have created another example program that performs a blocking operation in thread and changes the value of a Text View when the operation is finished.Note that in the quest for minimality I am utilizing some features of Gtkmm and C that are rarely shown in beginner examples (such as the ref-to-pointer and sigc::ref()).I believe the only way to connect with custom arguments is to use sigc::bind.I'm trying to figure out how to get a minimum amount of lines that will demonstrate outputting to a gui window (a textview widget) without the user having to click a button to get started.

If all the widgets were eliminated and it just had a simple gui window, it would be a bit easier for a beginner to work with.I'm sure, for experts there would hardly be any problems. A novice might have to keep everything intact to ensure that the code will compile, then try to figure out where to put his functions.As I mentioned, in my case, if I remove the buttons and progress bars, it becomes broken and I have to start back over with the full code and try a different approach. James [hidden email] On Fri, 2013-08-09 at -0700, Andrew Potter wrote: Mr. The last time I sent you a complete solution you never indicated how it was insufficient, so please be sure read this entire message.So I' trying to make the problem clear, so that whatever time and energy anyone applies would more likely answer the question. I should have run this line on Kjell's code before making a reference to 400 lines: // cli command begin cat * | egrep -v "^\s \*|^$|^/|^\s /" | wc // cli command end Without the comments and white space, I'd be substantially more lost.At present your presentation is extremely clear and takes me far into resolution of my immediate hurtle. I have a few more questions of which I'll try to organize and be clear when I post them.When excluding the important and very well documented comments of Kjell's example it comes up to nearly have my original number. Most of the confusion (for me) is the 11 widgets that, when I try to eliminate, breaks the code and I can't get it to work.

483

Leave a Reply