Le 06/05/2018 à 09:05, Nicola Fontana a écrit :
> Il Sat, 07 Apr 2018 06:25:52 +0200 Arun Gurung scrisse:
>
>> Hi,
>>
>> 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 de
Hi,
Le 10/06/2017 à 02:17, Karan Ahuja a écrit :
> I am looking to purchase a new laptop to work with gtk.
>
> Please recommend good laptop, operating system based on your experience.
>
> Thinkpad vs macbook?
Either work just fine, it really doesn't matter much wrt GTK, and I know
people happil
Le 27/01/2017 à 15:32, Mario Sanchez Prada a écrit :
> […]
>
> I know I arrive tremendously late to this thread, and I'm not even sure if
> this is going to be helpful for your situation, but just in case this is a
> small test application I wrote long ago to understand how the whole thing of
> At
Hi,
I'm trying to tackle https://bugzilla.gnome.org/show_bug.cgi?id=776854
down, and it seems that the unwanted events are originating from
gtkaccessibility.c's window_focus().
The problem here is that those AT events get emitted for e.g. global
keyboard shortcuts from the WM, even though no logi
Hi,
Thanks for those answers.
Le 29/12/2016 à 11:51, Alejandro Piñeiro a écrit :
>>> But fact is things like MATE-Panel make heavy use of those, so it'd be
>>> nice to have it work properly.
>
> Then perhaps it is about using AtkSocket/AtkPlug on MATE-Panel. But that
> is an advice given without
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 than the embedding one.
This leads to e.g. Orca finding them being par
Le 06/03/2015 02:12, Matthias Clasen a écrit :
> On Thu, Mar 5, 2015 at 3:23 PM, Olivier Fourdan wrote:
>
> […]
>
>> Ideally, GTK should be able to use CSD even without a compositor. The
>> only reason it requires a compositor is because it uses the shadows as
>> resize handles. Ideally, it shou
Le 23/12/2014 14:02, jcup...@gmail.com a écrit :
> I'm looking for the rational of using 'gint' instead of 'guint' in the
> call:
>
> g_ptr_array_set_size (GPtrArray *array, gint length);
>>>
I imagine that the use of a signed integer was an oversight at the time
whic
Hi,
Le 18/08/2014 19:55, Emmanuele Bassi a écrit :
> [...]
>
> when we introduced GL in the pipeline through the compositor 5 years
> ago, stuff that was 5 years old *at the time* already could run
> decently.
Not completely, no. I had (and still have) a really decent '07 card
(non-integrated 6
Le 06/08/2014 22:01, Krzysztof Kosiński a écrit :
> 2014-08-06 21:43 GMT+02:00 Colomban Wendling :
>> Le 06/08/2014 21:30, Krzysztof Kosiński a écrit :
>>> [Waf] does not require silly lists of files to work
>>
>> If that refers to using globs in the build system fi
Le 06/08/2014 21:30, Krzysztof Kosiński a écrit :
> [Waf] does not require silly lists of files to work
If that refers to using globs in the build system files, don't. Glob
showed on many a situation to be the source of various build problems,
including, but not limited to, a file to be missing f
Le 25/07/2014 23:46, Ameen Sayegh a écrit :
> [...] and I'm interested in C Language and its simplicity
I'm afraid that's not completely true :)
> [...]
>
> I have some question about the source code that I don't know what it
> does mean for example:
> gmem.h:120: "(void) (0 ? (gpointer) *(pp) :
36cd75609948e Mon Sep 17 00:00:00 2001
From: Colomban Wendling
Date: Tue, 24 Jun 2014 03:37:59 +0200
Subject: [PATCH] Don't leak the surface in gdk_cairo_create()
---
gdk/gdkwindow.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdk/gdkwindow.c b/gdk/gdkwindow.c
index 4e4ec98..68a75df
Le 24/06/2014 03:03, Jasper St. Pierre a écrit :
> Thanks, I managed to reproduce the issue with this. It only happens with
> thumbnails visible, though, which suggests that evince is doing
> something funny for the thumbnails view.
It happens with no sidebar at all here, so I don't think that's i
Le 24/06/2014 02:03, Jasper St. Pierre a écrit :
> I can't reproduce any issue in scrolling with evince locally -- does it
> only happen with certain documents? Can you point to a document where
> you have problems?
I doubt it's document-related, as it "worked" with the first three PDFs
I tried wi
Le 24/06/2014 00:02, Jasper St. Pierre a écrit :
> Hey everyone again
>
> [...]
>
> I've effectively pushed a revert of these changes:
>
> https://git.gnome.org/browse/gtk+/commit/?id=984e811c16891cb4945a090bea8ec9e81ce3dba6
> https://git.gnome.org/browse/gtk+/commit/?id=24b9e91f470d2f355c6e1901
Le 21/06/2014 03:00, Jasper St. Pierre a écrit :
> To better support Wayland with fewer copies and less drawing artifacts,
> I've pushed some potentially breaking changes to GDK, namely around
> gdk_cairo_create and gdk_window_begin_paint_region.
>
> https://git.gnome.org/browse/gtk+/commit/?id=d4
Le 09/05/2013 15:15, Nicola Fontana a écrit :
> Il Sun, 7 Apr 2013 23:50:10 -0400 Matthias Clasen
> scrisse:
>
>> Here is a patch that seems to work ok.
>
> The build fails during cross-compilation with:
>
> ./extract-strings.exe
> /home/aur/archlinux/fedora-mingw-w64-gtk3/src/gtk+-3.9.0/gtk/
Hi John,
Le 28/04/2013 18:30, John Emmas a écrit :
> On 28/04/2013 16:37, John Emmas wrote:
>> The only obvious difference I can see between your patch and my others
>> is that you seem to be using Git v1.7.10.4 whereas I'm still on v1.7.10.1.
>>
>> I'll ask on the TortioseGit mailing list to see
Le 28/04/2013 16:03, Colomban Wendling a écrit :
> Le 28/04/2013 09:32, John Emmas a écrit :
>> [...]
>
> 31fde567a95ff8f50b6b0e75d4010da9b73514ed broke it, but this looks very
> legitimate, so probably the test simply has to be updated.
Proposed patch fixing the test
Le 28/04/2013 09:32, John Emmas a écrit :
> The last time I updated glib (from git) was around a fortnight ago. I'm
> building using MSVC but up until now, everything's been building and
> running okay.
>
> This morning I updated to the latest git sources and re-built (after
> adding a new source
Hi,
Le 10/04/2013 19:52, Sindhu S a écrit :
> [...]
>
> Can you please answer my following questions:
>
> 1. Do you feel this is functionality is useful? (regardless of the path
> I proposed to accomplish it)
Maybe, but I don't personally find it particularly useful for me at first.
> If yes,
Le 16/11/2012 23:53, Timothy Arceri a écrit :
> Hi Guys, I'm after feedback on whether you guys think this is a good
> idea. For background I have been investigating bug
> https://bugzilla.gnome.org/show_bug.cgi?id=586367
>
> Basically what I've found is that gtk_file_chooser_set_local_only()
> is
Hi,
Le 22/06/2011 01:42, Dan Winship a écrit :
> On 06/19/2011 04:25 PM, Dmitry Matveev wrote:
>> My project includes writing a kqueue file monitoring backend for GIO, in
>> order to provide fast file monitoring to Glib/GIO-powered applications
>> on BSD systems.
>
> Cool. I took a quick look. It
Le 29/05/2011 01:06, Paul Davis a écrit :
> On Sat, May 28, 2011 at 5:01 PM, Benjamin Otte wrote:
>
> so lets take this particular point as an example of what i think the
> basic problem is here:
>
>> * There's button(s) that say ( Notes | Edit )
>> How are these buttons different from notebook
Le 02/10/2010 05:43, Matthias Clasen a écrit :
> * The rendering cleanup work has landed. This is a large change that
> affects many APIs.
> [...]
These are very interesting changes, I'm happy to see they work well now :)
> * Mouse wheel scrolling has been removed from GtkNotebook
I'm sad this
Martyn Russell a écrit :
> On 17/03/10 22:03, Andrew Cowie wrote:
>> in gtk/gtkbutton.c which after wading through several macros ends up as
>> a call to g_type_check_instance() in glib/gtype.c with some if/else
>> blocks around it.
>
> [snip]
>
>> So I'm wondering: can we [C, GTK] do away with o
Shaun McCance a écrit :
> On Wed, 2010-03-10 at 17:25 -0600, Jason D. Clinton wrote:
>> On Wed, Mar 10, 2010 at 4:50 PM, Cody Russell
>> wrote:
>> He
>> suggested that maybe there's a use for it in the case that you
>> have a
>> ton of notebook tabs open, but I'm n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kuczyński a écrit :
> Colomban Wendling pisze:
>> Simply because access to window->title will not be possible any
>> more, as I explained in another mail.
>>
>> - another mail: No, AFAIK, GSEAL_ENABLE is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kuczyński a écrit :
> A. Walton pisze:
>> 2009/4/12 A. Walton : ...
>>
>> gtk_window_set_title() is inside of gtk+ and won't need to
>> change. The macro is to prevent external applications from doing
>> window->title = whatever; and instead a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kuczyński a écrit :
> Colomban Wendling pisze:
>>> Ok I understand the idea, but... how work it? for example:
>>> --- struct _GtkWindow { GtkBin bin;
>>>
>>> gchar *GSEAL (title); --
Grzegorz Kuczyński a écrit :
> Colomban Wendling pisze:
>> AFAIK, it is used to hide members of GTK+ and GDK structures that
>> will become opaques in future releases (3.0 or so); then it makes
>> easy to see if a source must be updated not to use direct access
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Grzegorz Kuczyński a écrit :
> I want to know what gives macro GSEAL in struct GtkWindow.
AFAIK, it is used to hide members of GTK+ and GDK structures that will
become opaques in future releases (3.0 or so); then it makes easy to
see if a source m
Christian Dywan a écrit :
> This is how the current state is to my awareness:
>
> It is meant to work so that subclasses such a GtkHFoo and GtkVFoo
> behave the same as they used to, and can't flip. However if you use the
> originally abstract base class 'orientation' works as expected, at
> constr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tor Lillqvist a écrit :
> The existing g_utf8_strncpy() has it meaning characters. As such I
> think the name is bit unfortunate, because of the similarity to
> strncpy() but then different semantics of the "size" parameter.
>
> --tml
I don't think it
35 matches
Mail list logo
