<20170419112106.rfk2oxs5vfdn4...@archetype.pseudorandom.co.uk>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, 18 Apr 2017 at 23:05:04 +0100, Daniel Boles wrote:
> > Well, technically, code that relies on aliasing is
> > inherently buggy from the outset,
Just wondering what the position on this is. I've seen a few conflicting
indications:
(1) The new meson patches pass -fno-strict-aliasing to GCC and Clang:
https://git.gnome.org/browse/gtk+/commit/?h=wip/meson=1e3daf3178bb3db56ab12a55195969857f685101
The rationale is "We don't want to build buggy
On 3 May 2017 at 13:00, wrote:
> From: Murray Cumming
> To: Timm B?der
> Cc: gtk-devel-list
> Subject: Re: gtk4: gtk_box_pack_start()/end() porting
> Message-ID:
On 28 May 2017 at 13:00, wrote:
>
> Message: 1
> Date: Sun, 28 May 2017 10:55:21 +0800
> From: Cong Monkey
> To: gtk-devel-list
> Subject: will gobject-introspection build system migrate to cmake or
>
I can't speak for any maintainers, but I suspect that constantly pinging
like this does not have any significant - or at least significant *positive*
- effect on the chance of the tickets being bumped forward in the queue. I
believe that pinging is generally discouraged, especially when you do it
On 30 May 2017 at 05:44, Cong Monkey wrote:
> use msys2 in a massive visual studio based product is not a good idea,
>
Who ever said to do anything like that?
My point is MSYS2 is a near-complete Unix-like build environment, under
which you can simply build a native
>
> Date: Wed, 03 May 2017 15:45:14 +0200
> From: Murray Cumming
> To: Timm B?der
> Cc: gtk-devel-list
> Subject: Re: gtk4: gtk_box_pack_start()/end() porting
> Message-ID: <1493819114.24525.3.ca...@murrayc.com>
> Content-Type:
On 4 May 2017 at 10:44, Daniel Boles <dboles@gmail.com> wrote:
>
> I'm using GTK+ 3 (for the forseeable future) but have stopped using widget
> :margin and :spacing - juuust in case they get removed at some point in the
> future. There's a general trickle of things like
On 5 October 2017 at 10:46, Jean Delvare wrote:
>
> * While a number of people are advocating the ban of double-click and
> the use of single-click for everything to make computers easier to
> use by non-tech-savvy people and people with limited abilities,
> this change
I apologise if there is, if I just blocked most of that thread out of my
mind... but is there really a significant number of users out there who had
these complaints about double-click and genuinely think what we have now is
an unambiguous improvement? rather than just an apparent, superficial fix
On 12 October 2017 at 13:10, Daniel Boles <dboles@gmail.com> wrote:
> By my understanding, the explanation is this:
>
>- the Entry *is *right-aligned within its cell
>- but then the Grid is set to align fill and expand, so it expands
>empty space beyond the En
By my understanding, the explanation is this:
- the Entry *is *right-aligned within its cell
- but then the Grid is set to align fill and expand, so it expands empty
space beyond the Entry and the cell it's in
Assuming I understand this guide right, then it does kinda make sense to me.
>
> Date: Sat, 02 Sep 2017 21:10:56 +0200
> From: Ingo Br?ckl
> To: gtk-devel-list@gnome.org
> Subject: Re: Bug 554926 still in 2.24.31
> Message-ID: <59ab0245.000ac05b.bm...@wupperonline.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> after a few months have
>
> From: "Charles Lindsey"
> To: gtk-devel-list@gnome.org
> Subject: Re: [PATCH] file chooser: Restore consistent click behavior
> (for gtk3.20)
> It seems to me that those who are developing GTK are answerable to no-one,
> and it they continue to behave
The wildcard here, and what makes me confused as to whether my own
rationale makes sense, is that you have the grid expanding; I can't
immediately think of cases where I've used such a construct, so I don't
know what I expect it to do! It's also been a while since I thought about
how alignment and
I don't think we can say Broadway is "dead in the water"; there's a current
WIP branch for GTK+ 4 with new features and fixes.
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
On 6 May 2018 at 12:25, wrote:
> I have gobject-introspection-1.50.0-1.el7.x86_64 and gobject-
> introspection-devel-1.50.0-1.el7.x86_64. I tried to use a program like
> "menulibre" and "devedeng" and the developers say there is a bug in
>
I'd think the simplest option is to put your local GLib in your PATH with
higher priority, so that the non-absolute invocation of g-c-r finds your
one instead of the system one.
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
On 8 February 2018 at 12:01, wrote:
> Message: 2
> Date: Wed, 07 Feb 2018 13:45:47 +0100
> From: Christian Schoenebeck
> To: gtk-devel-list@gnome.org
> Subject: gtk_menu_item_set_accel_path()
> Message-ID:
On 27 December 2017 at 12:00, wrote:
> Date: Tue, 26 Dec 2017 21:06:30 +0100
> From: Tomasz G?sior
> To: gtk-devel-list@gnome.org
> Subject: Why these settings are deprecated?
> Message-ID:
On 11 March 2018 at 12:00, wrote:
> Date: Sat, 10 Mar 2018 15:19:06 +0100
> From: Luca Bacci
> To: gtk-devel-list@gnome.org
> Subject: Re: gtk on windows 10
> Message-ID:
>
On 6 March 2018 at 18:26, wrote:
> Message: 1
> Date: Wed, 13 Dec 2017 03:16:59 +0100
> From: S?bastien Le Roux
> To: gtk-app-devel-l...@gnome.org, gtk-devel-list@gnome.org
> Subject: GTK3 - GtkExpander problem, bug ?
>
On 16 April 2018 at 11:15, wrote:
>
> Regarding, the gestures, is there a tutorial of how to use them? The
> CustomWidgets tutorial mentions them, but then goes on to describe the
> button and motion notify events.
>
https://wiki.gnome.org/HowDoI/Gestures - to
I found these quite good (even though I wasn't using ListBox; they can be
generalised)
https://blog.gtk.org/2017/04/23/drag-and-drop-in-lists/
https://blog.gtk.org/2017/06/01/drag-and-drop-in-lists-revisited/
___
gtk-devel-list mailing list
24 matches
Mail list logo