2010/6/27 Mick :
> In veiw of the nightmare I've had finding non-trivial example code for
> assembling/implimenting gtk widgets recently I have decided to attempt
> to assemble a library of functions that impliment a task at a more
> advanced level than your typical 'Hello world' that abound.
>
> S
it would be good if the gtk tutorial would spent some pages on
threads. In these days where multicore cpu's are becoming the standard
a lot of programs can benefit from threads.
I'm willing to help with that, I contacted the webmasters from gtk.org
about it some time ago but I never received a rep
On 30 June 2010 01:57, Mick wrote:
> can anyone point me to an explanation (with examples) to help me
> understand running some dialogs in separate threads. (eg. help,
> preferences, etc)
It's almost always best to only have a single GUI thread in a gtk
application, in my experience.
Use non-mod
On 30 June 2010 02:57, Mick wrote:
> can anyone point me to an explanation (with examples) to help me
> understand running some dialogs in separate threads. (eg. help,
> preferences, etc)
The general recommendation is to avoid using any GTK+ object from
different threads (because it does not work
I'm trying to put custom content in GtkMenus... things like menu items, date
picker controls, lists and so on. These are all custom widgets that I can't
rewrite (easily). It seems that GtkMenus are very limited in what they can
display, just GtkMenuItems right? If I wrap my controls in GtkMenuIt
