Kind Sir,
Is it possible that I should be using the GTK Animation features to
display successive iterations of the cellular automata?
Alex
On 01/18/2018 02:04 PM, Daniel Boles wrote:
I get that it may have *seemed* to work, but it was under no
obligation to, and you started to see the evid
Thank you, will try version 1000+ ...
On 01/19/2018 09:29 AM, Kjell Ahlstedt wrote:
There is a chapter on multi-threaded programs in the gtkmm tutorial.
https://developer.gnome.org/gtkmm-tutorial/stable/chapter-multi-threaded-programs.html.en
It's said there that glib is thread-safe. What
There is a chapter on multi-threaded programs in the gtkmm tutorial.
https://developer.gnome.org/gtkmm-tutorial/stable/chapter-multi-threaded-programs.html.en
It's said there that glib is thread-safe. What is perhaps not stressed
enough is that gtk+ is not thread-safe. As Daniel has said, it's
I get that it may have *seemed* to work, but it was under no obligation to,
and you started to see the evidence of that. :P
Making a GTK+ instance global alone seems unable to solve the problem: what
you need is to stop manipulating it from threads that didn't initialise
GTK+ / aren't running the
Daniel,
I've designed things this way because I can't have an "interruptible
loop" using Gtk. After much effort this was the only way I ever found
to do it.
However, what you said gives me an idea! I'm currently creating the
Pixbuf, whose data I'm manipulating, in the thread. I'll instead
The general rule is that only the thread in which GLib/GTK+/etc. was
initialised should ever do anything with widgets or other non-trivial
objects. If you're doing that, all bets are off. But it's not really clear
whether you are.
___
gtkmm-list mailing l
Hello, Help Please,
I have written an initial version of a simple Cellular Automata program
using
GTKmm for the UI. Mostly the program works fine, however sometimes the
program
stops displaying the sequence of Gdk::Pixbuf that it generates. This happens
when I'm interacting with the UI of anot
