Hi all;
next week, on May 1st, this list will be archived[0]. This means no new
subscriptions, and no new email.
If you have questions about GTK, GLib, and the rest of the core GNOME
development platform, you can use the Discourse[1] instance hosted on GNOME
infrastructure; we have a Platform/Cor
Hi all;
as announced in:
https://mail.gnome.org/archives/gtk-devel-list/2019-March/msg0.html
we have created a Discourse instance available at:
https://discourse.gnome.org
After testing it for the past couple of weeks, we're very satisfied with
how the platform behaves, so we are going
r
non-sensical, not emitted, or not possible by design.
This is why I said: "there is no way to know".
Ciao,
Emmanuele.
On Sun, 3 Mar 2019 at 16:10, Paul Davis wrote:
>
>
>
> On Sun, Mar 3, 2019 at 6:26 AM Emmanuele Bassi via gtk-devel-list <
> gtk-devel-list@gnome.o
On Sun, 3 Mar 2019 at 12:58, John Emmas wrote:
> On 03/03/2019 11:22, Emmanuele Bassi wrote:
>
> On Sun, 3 Mar 2019 at 11:09, John Emmas wrote:
>
>> Sorry to ask a dumb question...
>>
>> What does it mean if a widget is "mapped" ?
>>
>
>
On Sun, 3 Mar 2019 at 11:09, John Emmas wrote:
> Sorry to ask a dumb question...
>
> What does it mean if a widget is "mapped" ?
>
It means that:
- the widget is visible
- the widget is realized
- all its ancestors up to the top level window are mapped
Only mapped widgets are drawn and can
Note: for those who prefer email, we've written down a handy guide on how
to use email with Discourse:
https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
Ciao,
Emmanuele.
On Fri, 1 Mar 2019 at 15:50, Emmanuele Bassi wrote:
> And, of course, I forgot the lin
And, of course, I forgot the link: https://discourse.gnome.org
Embarrassing.
Ciao,
Emmanuele.
On Fri, 1 Mar 2019 at 15:41, Emmanuele Bassi wrote:
> Hi all;
>
> after the discussion[1] last month, and the feedback received (both on
> list and off), we decided to trial a Discourse
Hi all;
after the discussion[1] last month, and the feedback received (both on list
and off), we decided to trial a Discourse instance on the GNOME
infrastructure.
The Platform/Core sub-category is meant to be used for all discussions
about GTK, GLib, GdkPixbuf, Pango, and other core libraries of
On Wed, 6 Feb 2019 at 12:19, Emmanuele Bassi wrote:
>
> The main differences are that you’d need a different subscription account
> than the existing one, and that you wouldn’t have the weekly digests, as
> far as I can see.
>
It turns out I was wrong: Discourse has "weekl
On Thu, 7 Feb 2019 at 00:54, wrote:
> > We already looked at Hyperkitty, and found it fairly limited in
> > functionality. Avoiding Hyperkitty is what led us to Discourse in the
> > first place.
> Can you link that discussion please?
It was on IRC and in person discussions, and private emails b
eplying to topics
The Fedora (Silverblue) and Ubuntu communities already use Discourse, for
instance; the SDL community also does.
Ciao,
Emmanuele.
On Wed, 6 Feb 2019 at 12:46, Emmanuele Bassi wrote:
> [Cross-posted to various relevant mailing lists; please, reply to
> gtk-devel-list]
&
On Wed, 6 Feb 2019 at 15:11, Charles Lindsey wrote:
>
>
> On 06/02/2019 11:46, Emmanuele Bassi via gtk-devel-list wrote:
> > [Cross-posted to various relevant mailing lists; please, reply to
> > gtk-devel-list]
> >
> > As part of an attempt at making GTK more fri
Hi;
On Wed, 6 Feb 2019 at 13:10, Reuben Rissler wrote:
>
> To introduce myself, I only am using Gtk for 3 years, but really like
> the infrastructure / people / open source surrounding Gtk. I am
> sometimes seen as 'theGtknerd'.
>
>
> On 02/06/2019 06:46 AM, Emm
[Cross-posted to various relevant mailing lists; please, reply to
gtk-devel-list]
As part of an attempt at making GTK more friendly to newcomers, I and other
core developers were thinking of moving the mailing lists from the current
mailman installation to Discourse:
https://discourse.org/
Pos
Hi all;
tl;dr: GTK is GTK, not GTK+. The documentation has been updated, and the
pkg-config file for the future 4.0 major release is now called "gtk4"
over the years, we had discussions about removing the "+" from the project
name. The "plus" was added to "GTK" once it was moved out of the GIMP
s
On Sun, 16 Sep 2018 at 10:47, John Emmas wrote:
> On 15/09/2018 18:48, John Emmas wrote:
> >
> > Do you happen to know if the tiff library has its own mailing list? I
> > haven't had much success in finding one
> >
>
> In fact I'll need the mailing list for gdk-pixbuf now - except that I
> ca
Are you trying to access a repository using a `git://` URL? That has been
deprecated a long time ago, for security reasons, and with GitLab it was
removed altogether.
Ciao,
Emmanuele.
On Thu, 6 Sep 2018 at 14:09, John Emmas wrote:
> Hi guys - sorry for posting this here but I've tried gnome's
On Wed, 5 Sep 2018 at 19:25, Magnus Bergman
wrote:
> On Wed, 5 Sep 2018 17:28:22 +0100
> Emmanuele Bassi wrote:
>
> > We're phasing out Cairo in favour of the CSS rendering model,
> > implemented on top of OpenGL and Vulkan, as it's the API that most
> > cl
Hi;
On Tue, 4 Sep 2018 at 23:19, Magnus Bergman
wrote:
> Over the years it has been discussed from time to time to replace
> gdk-pixbuf with something else[1][2]. Something was even in the making
> (I guess over ten years ago) but it never replaced gdk-pixbuf
> apparently. Now I don't even remem
ib's CI for each
> tag, so it can be taken from artifacts. I don't know if it gets
> published from there, but we could do something. Emmanuele Bassi
> probably knows more about this mechanism.
>
It doesn't get published, only built and stored as artefacts – though it&#x
With Python 2.x getting EOL in less than 2 years, I suspect that commercial
distros will need to provide Python 3 pretty quickly.
Ciao,
Emmanuele.
On Fri, 1 Jun 2018 at 21:10, Christian Hergert wrote:
> On 06/01/2018 08:10 AM, xclae...@gmail.com wrote:
> > Disclaimer: I'm not a GLib maintainer
The migration is complete.
Ciao,
Emmanuele.
On 1 May 2018 at 09:02, Carlos Soriano wrote:
> Hello,
>
> Tomorrow Wednesday 2nd we're going to do the bug migration of gtk+. Since
> gtk+ has been for some time in GitLab, probably most of you are subscribed
> to notifications.
>
> This is a call t
On 16 April 2018 at 19:32, Emmanuele Bassi wrote:
>
> * Migrate what's left at the end
>>
>
> We're in the process of migrating: https://gitlab.gnome.org/
> Infrastructure/GitLab/issues/228
>
> This will take a while once it starts; I'll send anot
Hi all;
it's time for an update.
On 2 February 2018 at 14:04, Matthias Clasen
wrote:
> Hey Carlos,
>
> we discussed gitlab migration for gtk here at the hackfest. Our
> conclusions were as follows:
>
> * We want to migrate the git repository as soon as possible
>
The repository was migrated su
On 16 April 2018 at 10:19, Dov Grobgeld wrote:
> Hi all,
>
> After lots of years I finally got around to porting my widget
> GtkImageViewer to gtk3. After doing lots of reading of man pages, did I
> realize that i can turn off double buffering.
>
I wonder what kind of man pages did you read, con
On Fri, 23 Mar 2018 at 09:07, John Emmas wrote:
> On 23/03/2018 08:53, LRN wrote:
> > On 23.03.2018 11:08, John Emmas wrote:
> >> has the gtk repo moved recently (or has the gtk-2-24 branch
> >> been deleted somehow?)
> >>
> >> [...]
> >>
> >> Is it no longer hosted at git.gnome.org maybe?
> > Co
On Fri, 2 Mar 2018 at 00:03, Alex ARNAUD wrote:
> Le 01/03/2018 à 16:32, Emmanuele Bassi a écrit :
> > that the current GNOME Shell already has logic for zoom, color
> > inversion, and other effects, it’s perfectly capable of dealing with
> > these requirements.
>
&g
On Thu, 1 Mar 2018 at 20:48, Samuel Thibault
wrote:
> Hello,
>
> Emmanuele Bassi, on jeu. 01 mars 2018 14:42:27 +0700, wrote:
> > On 26 February 2018 at 17:49, Samuel Thibault
> > wrote:
> > > Hello,
> > >
> > > So, I also saw the removal
On 26 February 2018 at 17:49, Samuel Thibault
wrote:
> Hello,
>
> So, I also saw the removal of generic modules.
>
> Unfortunately we currently need it for implementing perfect zoom feature
> :)
I don't know what a "perfect zoom feature" is — but zooming on a
window should be part of the display
they expose their menus on the session bus, either
through the GMenu API directly, or by implementing the same DBus API
exposed by GTK.
Ciao,
Emmanuele.
> On Sun, 2018-02-25 at 09:54 +, Emmanuele Bassi wrote:
>> Hi;
>>
>> On Sun, 25 Feb 2018 at 09:18, Philipp Emanuel Weid
Hi;
On Sun, 25 Feb 2018 at 09:18, Philipp Emanuel Weidmann <
p...@worldwidemann.com> wrote:
> Greetings,
>
> I am the author of Plotinus[1], a GTK+ module that provides a
> searchable command palette to GTK+ applications. Recently, it was
> brought to my attention[2] that module loading has been
On 10 February 2018 at 21:26, Kristian Rietveld wrote:
>
>> On 05 Feb 2018, at 11:37, Emmanuele Bassi wrote:
>>
>> Of course if we get a positive response that the bug is still there
>> we're going to migrate it and keep track of it.
>>
>>> With t
doesn't like being called out. I'll just remember it for the next
time you open a bug, explaining what *I* have to do, without even
bothering to attach a patch. Or reply "this bug still exists" without
testing it, because you're too busy with your own stuff.
Ciao,
Emman
On 5 February 2018 at 10:40, Timm Bäder wrote:
> On 05.02, Clemens Eisserer wrote:
>> So back to the original question: How does the GTK+ project make sure
>> to spot performance regressions when they are introduced?
>> And if there is nothing automated, would there be interest in such a
>> projec
On 4 February 2018 at 20:52, Morten Welinder wrote:
> As a general principle, you should only ask bug reporters to do work if you
> intend to do something with the answer. Or, with other words, it really is
> not nice to keep asking "is that bug still there?" until they get tired of the
> busywor
On 5 February 2018 at 09:35, Clemens Eisserer wrote:
> Hi there,
>
> I wonder - is there any automatic / nightly performance regression
> testing done against GTK+ development snapshots, like it is done by
> other performance-sensitive open-source projects (e.g. mozilla
> firefox)?
No.
Ideally,
On 2 February 2018 at 15:04, Matthias Clasen wrote:
> Hey Carlos,
>
> we discussed gitlab migration for gtk here at the hackfest. Our conclusions
> were as follows:
>
> * We want to migrate the git repository as soon as possible
> * For bugs:
> * Do a sweep now, close all >5 year old bugs, needi
Hi;
On 24 January 2018 at 13:20, John Emmas wrote:
> In my November 2017 version, the most recent commit for
> 'gobject/glib-genmarshal.in' is:- is #100b83a7fa ("genmarshal Only wrap body
> prototypes in C++ guards"). But a couple of further commits got added since
> then. I'm pretty certain o
On 22 January 2018 at 09:28, Philip Withnall wrote:
> On Wed, 2018-01-17 at 18:15 +0100, Bastien Nocera wrote:
>> On Wed, 2018-01-17 at 13:15 +0100, Bastien Nocera wrote:
>> > Hey,
>> >
>> > I wanted to start a discussion about replacing
>> > GnomeDesktopThumbnail
>> > with an API that would live
Hi;
creating GObject classes with modern best practices is matter of calling:
G_DECLARE_FINAL_TYPE
or:
G_DECLARE_DERIVABLE_TYPE
in your header file, and:
G_DEFINE_TYPE
in your source file. Anything else is usually dependent on what your
class is going to contain; properties? Signals? A
Hi;
On 8 January 2018 at 13:20, Nitin Jain wrote:
> Is there any QNX port available for glib .
We don't manage packaging of GLib ourselves, if that's what you're
asking. We usually defer to whatever downstreams exist for any given
platform.
> Any pointers will be very helpful if we want to por
On 26 December 2017 at 20:06, Tomasz Gąsior wrote:
> I would like to ask question directly to main GTK developers. Why these
> Xsettings are deprecated?
XSettings are an X11-only concept that does not translate to any other
windowing system platform supported by GDK.
You're probably thinking of
On 23 December 2017 at 13:47, Salvatore De Paolis wrote:
> On Wed, 13 Dec 2017 15:08:46 -0800
> Christian Hergert wrote:
>
>> Ardour could never move to Gtk3 because a number of VST plugins use Gtk2
>> and you cannot mix both into the same process space. DAW authors will
>> often cite the necessi
On 17 December 2017 at 23:14, Daniel Kasak wrote:
>> Just one example, gtk3 (yes 3, not even 4) is currently completely
>> unusable on
>> Mac, so I sent a patch to fix this:
>>
>> https://bugzilla.gnome.org/show_bug.cgi?id=791174
>>
>> I know my patch is suboptimal, but to make this clear
On 17 December 2017 at 23:28, Tomasz Gąsior wrote:
> It is possible to build GTK3 without Accessibility Toolkit dependency? How
> can I do it?
You can't: ATK types are exposed in the GTK API.
Ciao,
Emmanuele.
--
https://www.bassi.io
[@] ebassi [@gmail.com]
___
On 14 December 2017 at 18:42, Sébastien Wilmet wrote:
> On Wed, Dec 13, 2017 at 04:55:41PM +0000, Emmanuele Bassi wrote:
>> The API that gets removed in GTK+ 3.9x is deprecated in GTK+ 3.22 beforehand.
>
> No, that's not true.
>
> A recent example:
> https://git.gno
On 13 December 2017 at 16:34, Christian Schoenebeck
wrote:
> On Mittwoch, 13. Dezember 2017 12:33:34 CET Emmanuele Bassi wrote:
>> On 13 December 2017 at 12:05, Sébastien Wilmet wrote:
>> > Ideally, a new major version of a library should only remove deprecated
>> > A
On 13 December 2017 at 12:05, Sébastien Wilmet wrote:
> Ideally, a new major version of a library should only remove deprecated APIs.
I'm having major flashbacks from the same discussions we had at Gran
Canaria, when we planned 3.0 — with people asking for releasing 3.0
only with sealed data str
On 8 December 2017 at 11:26, Philip Withnall wrote:
> If anybody encounters any problems with this, please comment on the bug
> report:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=790697
As a side note: I've started a full Continuous rebuild, so if there
are projects that indeed break with t
Hi Felipe;
You probably wanted to send this email to gtk-devel-list, not
gtk-app-devel-list.
On Sat, 25 Nov 2017 at 12:41, Felipe Borges
wrote:
> Hi,
>
> I have been looking for a clean way of updating my widget's css
> properties programmatically at runtime.
>
> Basically I have a css animatio
On 20 November 2017 at 17:34, Andrea Zagli wrote:
> Il giorno lun 20 nov 2017 16:02:11 CET, Emmanuele Bassi ha scritto:
>
>> Hi;
>>
>> On 20 November 2017 at 14:52, Andrea Zagli via gtk-devel-list
>> wrote:
>>>
>>> do you plan to port (i don
Hi;
On 20 November 2017 at 14:52, Andrea Zagli via gtk-devel-list
wrote:
> do you plan to port (i don't know if "port" is the right word) glib/gtk to
> webassembly?
There are no plans that I'm aware of, nor use cases that have
materialised that would require such a port.
Ciao,
Emmanuele.
--
Hi;
thanks for your patch; GTK uses Bugzilla to track issues,
contributions, and requests for enhancements.
Please, file a bug at:
https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B and attach
your patch, so it won't get lost and will be properly reviewed.
It would be stellar if you created
On 7 September 2017 at 16:35, John Emmas wrote:
> gdk-pixbuf and gdk+2 both built fine for me. The only odd thing I noticed
> was when building gtk (from gtk-2-24) I saw quite a few warning messages
> looking like this:-
>
> WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead
>
In GLib 2.52, glib-genmarshal is a C program. In GLib master, which
will become GLib 2.54 soon, glib-genmarshal is a Python program.
The change from C to Python will *not* be backported to GLib 2.52.
Ciao,
Emmanuele.
On 6 September 2017 at 16:41, John Emmas wrote:
> Hi guys...
>
> pytho
On 25 August 2017 at 14:39, John Emmas wrote:
> On 25/08/2017 10:17, Emmanuele Bassi wrote:
>>
>> The Visual Studio project files are not up to date, and since we're
>> switching the build to Meson, I don't think they'll stay in tree much
>> longer.
>
On 25 August 2017 at 10:13, John Emmas wrote:
> Please point me to the right place (if this isn't the correct mailing
> list...)
>
> I've just updated gdk-pixbuf from git master. 'gdk-pixbuf.c' used to
> contain this #include at line 38:-
>
> #include "gdk-pixbuf-marshal.c"
>
> However... i
Could you please open a bug?
Ciao,
Emmanuele.
On 24 August 2017 at 18:37, John Emmas wrote:
> On 19/08/2017 12:16, John Emmas wrote:
>
>
> I still don't understand why this line (in commit #fe2a9887a8):-
>
> elif os.name == 'nt'
>
> got changed to this:-
>
> elif os.basename(fil
On 15 August 2017 at 04:09, Chun-wei Fan (范君維) wrote:
> Hi,
>
> Thanks to Emmanuele for giving me the credit here :)
Absolutely well earned.
> Emmanuele Bassi 於 2017/8/15 上午 05:46 寫道:
>>
>> The change means that GTK+ master now has a build-time dependency on:
>>
&g
Hi all;
executive summary: the master branch of GTK+ now builds with Meson,
and the Autotools build system files have been dropped.
The documentation has been updated to reflect the new build system —
as well as, in some cases, the past 10 years of development.
The change means that GTK+ master
On 2 May 2017 at 00:09, Matthias Clasen wrote:
> On Thu, Apr 27, 2017 at 10:29 AM, Emmanuele Bassi wrote:
>>
>> For command line parsing I'd actually favour a slightly bolder
>> approach of deprecating GOptionContext, and having something slightly
>> more modern
On 27 April 2017 at 22:56, Brion Vibber wrote:
> GTK+3 added native support for user interface scaling to support HiDPI
> displays with consistently sized resources and widgets, with the limitation
> that the scaling factor is an integer (1x, 2x, 3x...)
It's not really a "limitation": it's purpos
For command line parsing I'd actually favour a slightly bolder
approach of deprecating GOptionContext, and having something slightly
more modern — in terms of being bindable in other languages, and
well-integrated with API like GApplication.
For instance, something similar to [clap.rs][0].
Ciao,
On 19 April 2017 at 13:29, Morten Welinder wrote:
> glib (etc) _is_ stomping on the standard in a hundred different ways. Some
> are for performance -- \0 filling, for example -- while others are pure
> laziness
> and ignorance such as variables called "read" or macros name starting with
> "E"
I added the compiler warnings by merging what I use in libepoxy,
graphene, json-glib, and what's in the existing autotools build. That
was done mostly to get the ball rolling, not as a commentary on
whether strict aliasing rules are good or bad.
In general, I'd expect us to review the compiler war
On 17 April 2017 at 10:38, John Emmas via gtk-devel-list
wrote:
> so all three functions are getting exported - BUT - if I examine the
> corresponding link lib, I can see a reference to g_mkstemp_full(). I can
> also see a reference to g_mkstemp_utf8(). But there's no reference to
> g_mkstemp().
On 14 February 2017 at 12:25, Rúben Rodrigues wrote:
> Hi,It gives me this error:
> 
> I'm sorry for this basic questions for you but i don't see tutorials that
> explains more detailed to understand..
>
>
> i'm new on Linux and gtk+. I'm trying to migrate an application make with
> gtk+2.0, an
This issue relates to gdk-pixbuf, which does not have the C89 fallback code
that GTK has.
Personally, I'd be completely open to stop suppprting MSVC older than 2015
in newer releases of G* libraries and start requiring C99 features, like we
did for GTK in the master branch. Nevertheless, I underst
Hi;
On 4 February 2017 at 22:54, Ferenc Engárd wrote:
> Thanks for the answers!
>
> I have found the root cause in my code: I realized that GtkGlArea render
> calls are not called automatically for each screen refresh, and the observed
> ~40Hz was coming from my program (a timer I already forgot
Hi John;
On 4 February 2017 at 18:17, John Emmas via gtk-devel-list
wrote:
> On 04/02/2017 16:07, Martin Guy wrote:
>>
>> On 04/02/2017, John Emmas via gtk-devel-list
>> wrote:
>>>
>>> I took a quick look through glib, gtk+ (v2) and gdk-pixbuf but I
>>> can't see lrint getting used anywhere else
Hi;
On 29 January 2017 at 10:00, Sébastien Wilmet wrote:
> On Sat, Sep 03, 2016 at 02:09:04PM +0100, Emmanuele Bassi wrote:
>> https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/
>
> In the above announcement, you've written:
I didn
Hi Stefan;
On 29 December 2016 at 22:55, Stefan Sauer wrote:
> Sorry for reviving the thread. What if upstream lib ship a suppression
> file and add a pkg-config variable pointing to it? Then apps can use
> $PKG_CONFIG --variable=valgrind_suppressions gtk+-3.0
> to collect those and e.g. export
Hi;
On 28 December 2016 at 17:29, Colomban Wendling wrote:
> Hi,
>
> It seems that GtkSocket and GtkPlug aren't tied together at the
> accessibility level: e.g. the ATSPI tree from Accerciser shows them
> separately, and atspi_accessible_get_application() returns the embedded
> application rather
Hi;
No: HiDpi (window scaling) support is not something available in GTK 2.x,
and it cannot be backported to it from GTK 3.x, given the complex redesign
of the internals and the necessary API additions.
You should either port to GTK 3.x (for which there's a branch of Gtk#) or
you will have to shi
Hi Alex;
On 15 December 2016 at 15:26, Alexander Larsson wrote:
> I just read through the wip/otte/rendermode branch, and I must say I
> really like it. It makes it very explicit that the rendernodes are
> immutable. For instance, there is no "append" operation or any setters
> for any data (othe
Hi;
On 16 December 2016 at 15:08, Owen Taylor wrote:
>> First of all, generally you have to supply entire buffers that have
>> valid content everywhere. If you're lucky you can use extensions like
>> buffer age so that you can track which part of the back buffer is up-
>> to-date, but that requi
Hi;
On 28 November 2016 at 18:48, Alex Henrie wrote:
> Can I get some feedback on my patch for
> https://bugzilla.gnome.org/show_bug.cgi?id=774738 ?
>
> If this bug is not going to be fixed then I'll make sure to put null
> checks before calls to g_error_free, but if it's going to be fixed
> soo
Hi;
On 3 November 2016 at 18:25, Olivier Brunel wrote:
> On Sun, 4 Sep 2016 13:23:14 +0530
> Samik Ganguly wrote:
>
> (...)
>> Now, if the path "0" refers to root node, how can it have a parent to
>> move to? After calling this method on path, the path isn't valid
>> anymore and fails to be conv
Hi;
On 12 August 2016 at 05:22, narcisse doudieu siewe
wrote:
> Hi every body,
>
> is it possible to anumate row insertion and deletion on
> GtkLixbox and more generaly in GtkTreeview? how can
> I do that?
No, it's not possible.
Ciao,
Emmanuele.
--
https://www.bassi.io
[@] ebassi [@gmail.com
Hi;
On 3 September 2016 at 10:27, Sébastien Wilmet wrote:
> The versioning looks much better. Small detail, during the next
> development cycle, the alpha/beta/rc versions will be 3.89.x, with the
> 3.90.0 version released in March 2017, right?
Starting at ".90" has a good round number feeling
Hi all;
after the Toronto hackfest of June 2016, the discussion on the
gtk-devel mailing list, and after various discussions at GUADEC 2016
in Karlsruhe, the GTK team has reached a consensus on how the GTK+
project should perform its releases.
You can find the whole description of the motivations
id you watch his video?
>
> On Sun, Aug 21, 2016 at 3:07 AM, Emmanuele Bassi wrote:
>>
>> Hi;
>>
>> thanks for your email.
>>
>> GTK+, as a project, tracks bugs and enhancements in Bugzilla -
>> https://Bugzilla.gnome.org/enter_bug.cgi?product=gtk%2b -
Hi;
thanks for your email.
GTK+, as a project, tracks bugs and enhancements in Bugzilla -
https://Bugzilla.gnome.org/enter_bug.cgi?product=gtk%2b - instead of the
mailing list, which is only meant for discussion.
Additionally, the latest stable version of GTK+ is 3.20, and we plan to
release GTK
Hi;
On Sunday, 14 August 2016, Chris Vine wrote:
> On Sun, 14 Aug 2016 21:22:06 +0200
> Sébastien Wilmet > wrote:
> > On Sun, Aug 14, 2016 at 07:17:34PM +0100, Chris Vine wrote:
> > > On Sun, 14 Aug 2016 13:40:55 +0200
> > > Sébastien Wilmet > wrote:
> > > > When GTK+ breaks the API, it doesn't
Hi;
On 3 August 2016 at 19:35, John Emmas wrote:
> On 03/08/2016 18:46, Emmanuele Bassi wrote:
>>
>> This is likely a MSVC 8 issue. The GOBJECT_IF_DEBUG macro expands the
>> second argument to a code block, and it seems MSVC 8 has issues when
>> that includes
Hi;
On 3 August 2016 at 18:36, John Emmas wrote:
> Hi there - I just came across a problem after updating libglib to the latest
> git master (my last update was about a fortnight ago).
>
> I'm building with MSVC 8 and when I try to compile 'gobject/gobject.c' the
> Release version compiles fine b
Hi;
as this question does not have anything to do with the development of GTK+,
you should likely open a bug against gnome-terminal:
https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-terminal
Ciao,
Emmanuele.
On Saturday, 23 July 2016, cedlemo wrote:
> Hi,
>
>
> I am surprised by the se
Hi Alex;
I've been mulling over this for a bit, and started working on what I
think is a feasible solution.
On 14 July 2016 at 22:09, Alexander Larsson wrote:
> (Sorry for breaking threading, etc, posting from my phone)
>
> So, I think you misunderstood my opinion. I think the change in API to m
On 11 July 2016 at 12:16, Emmanuele Bassi wrote:
> Personally, I think the new behaviour of throwing away the render tree
> after each frame makes the code much more resilient, especially in the
> perspective of a future "off the main thread" rendering scenario —
> though I
Hi Alex;
thanks so much for this review.
On 8 July 2016 at 10:15, Alexander Larsson wrote:
> So, I had a quick look at the gsk-render branch. I don't really have
> much time for an in depth review, but here are some issues i saw:
>
> The first one is a detail in the gl renderer. As opposed to a
Hi;
On 25 June 2016 at 12:45, Samik Ganguly wrote:
> Hello Gtk+ developers,
if you're trying to reach the GTK+ developers you're using the wrong
mailing list; you want to use gtk-devel-list. I've added the list to
the Cc:
> Gtk+ implements various CSS3 functionality so that widgets can be s
Hi;
On 13 June 2016 at 16:18, Ingo Brückl wrote:
> Emmanuele Bassi wrote on Mon, 13 Jun 2016 15:43:21 +0100:
>
>> GLib and GTK+ track patches on Bugzilla; could you please open a bug at:
>
>> https://bugzilla.gnome.org/enter_bug.cgi?product=glib
>
>> and attac
Hi;
On 13 June 2016 at 15:32, Ingo Brückl wrote:
> I was upgrading glib from v2.44.1 to v2.48.1 and having some problems with
> the test suite.
>
> Please consider the following 6 patches. After having applied them locally,
> the test suite stopped from failing and ended error-free.
Thanks for y
Hi;
On 4 May 2016 at 05:47, Ricardo Wurmus wrote:
>
> Ricardo Wurmus writes:
>
> [...]
>
>> This is why I would like to propose two patches, one against GTK+ 2.x
>> and the other against GTK+ 3.x, introducing the environment variables
>> GTK2_PATH and GTK3_PATH, which allow users to specify addi
Hi;
On 19 March 2016 at 18:03, Randall Sawyer wrote:
> The concision of "GUString" over "G_UTF8String" reflects the concision of my
> thoughts over what they were at the beginning of this thread.
Since you've brought it up multiple times, I wanted to ensure you
understood this particular point..
Hi;
The patch is marked as "accepted/commit now". If you don't have the commit
bit on git.gnome.org then you'll have to wait until the maintainer commits
it for you. This usually happens before a release is planned.
Ciao,
Emmanuele.
On Thursday, 10 March 2016, Friedrich Beckmann
wrote:
> Hi,
Hi;
On 2 February 2016 at 12:29, SAHIL SAREEN wrote:
>
>> org.gnome.foo-bar
>>
>>please consider renaming it to:
>>
>> org.gnome.FooBar
>
> I also see a lot off apps not using the "org.gnome" prefix, all the
> games(Except org.gnome.Hitori.desktop) actually.
> Maybe we should fix that as well.
Hi all;
as you may have noticed[0] from Planet GNOME, there has been some
effort to start generating nightly XDG App bundles of various GNOME
applications.
This effort, amongst other things, allows us to see what's currently
required to get GNOME apps in a bundle.
The first hurdle has been that
Hi;
Thanks for you patches.
GLib uses Bugzilla[0] to track patches and contributions. Please, use:
https://bugzilla.gnome.org/enter_bug.cgi?product=glib
to file a bug report and attach your patches there.
Thanks again!
Ciao,
Emmanuele.
On 25 January 2016 at 15:08, Frediano Ziglio wrote:
Hi;
On 3 November 2015 at 16:19, John Emmas wrote:
> On 3 Nov 2015, at 11:50, Simon McVittie wrote:
>
>>
>> Perhaps the "inline" stuff should move to gtypes.h, or somewhere even
>> lower-level, like glibconfig.h?
>>
>
> As an experiment, I tried moving the inline stuff out of gutils.h and
> stra
1 - 100 of 577 matches
Mail list logo
