On 09/28/2009 06:11 PM, Allin Cottrell wrote:
> I'm not sure if the solution Morten advocates -- namely, applying
> the GSEAL principle internally -- is the best one, although maybe
> it is.
It's not even necessary. Gtk can access struct members directly if
desired (for performance reasons, or w
On Mon, 28 Sep 2009, Morten Welinder wrote:
> A long time ago GTK+ was a collection of widgets. If you did
> not like what you had, you could grab the source of one of the
> widgets and change it to do whatever you needed it to do.
>
> This is increasing no longer the case -- in-tree Gtk+ are no
Sven Neumann wrote:
> Hi,
>
> On Mon, 2009-09-28 at 02:00 -0400, Thomas Jaeger wrote:
>> - if (!strcmp (tmp_name, "pointer"))
>> -gdkdev->info.source = GDK_SOURCE_MOUSE;
>> - else if (!strcmp (tmp_name, "wacom") ||
>> - !strcmp (tmp_name, "pen"))
>> -gdkdev->info.source = GDK_SO
Hi,
On Mon, 2009-09-28 at 02:00 -0400, Thomas Jaeger wrote:
> - if (!strcmp (tmp_name, "pointer"))
> -gdkdev->info.source = GDK_SOURCE_MOUSE;
> - else if (!strcmp (tmp_name, "wacom") ||
> - !strcmp (tmp_name, "pen"))
> -gdkdev->info.source = GDK_SOURCE_PEN;
> - else if (!strcmp
A long time ago GTK+ was a collection of widgets. If you did not like
what you had,
you could grab the source of one of the widgets and change it to do whatever you
needed it to do.
This is increasing no longer the case -- in-tree Gtk+ are now special
and programmed
using a different API than out
On Mon, 2009-09-28 at 02:00 -0400, Thomas Jaeger wrote:
> This is necessary since wacom devices don't have predictable names
> anymore. Please let me know if I need to open a bug report for this issue.
Looks sane to me. Pushed.
___
gtk-devel-list mail
