On Sun, Jul 22, 2018 at 11:58 PM, scott via gtk-list
wrote:
>
>
> As an example, my application takes no inputs. You don't click on it. You
> look at it. Originally it wasn't a GUI at all; it was an invisible service.
> But letting it paint a screen with current status was deemed useful, so I
> b
On 07/22/2018 02:37 PM, Paul Davis wrote:
On Sun, Jul 22, 2018 at 1:26 PM, scott via gtk-list
mailto:gtk-list@gnome.org>> wrote:
Abolish the concept of a main gtk thread. "Anything anywhere and
real soon now" should be the motto.
this is a terrible, terrible idea.
the benefits of a
On Sun, Jul 22, 2018 at 1:26 PM, scott via gtk-list
wrote:
> I'm new here, and here to cause some trouble. I just wrote my first GTK+3
> app - or rather, I adapted an existing C++ program to give it a GUI with
> GTK+3, and the distinction is important for reasons I'll make clear. It
> wasn't a fu
All of which is why I'm slowly abandoning GTK for Qt. GTK has been
turned into an inflexible bureaucratic nightmare. I can either spend my
time trying to figure out how to outwit the limitations GTK has been
saddled with, or I can spend my time learning a new toolkit. The latter
is far more
I'm new here, and here to cause some trouble. I just wrote my first
GTK+3 app - or rather, I adapted an existing C++ program to give it a
GUI with GTK+3, and the distinction is important for reasons I'll make
clear. It wasn't a fun experience, and I'll try to keep ranting to a
minimum, but I'm
