Re: How to get a "traditional" file-chooser

2017-09-15 Thread Emmanuele Bassi
On 15 September 2017 at 20:33, Chris Moller wrote: > There are some major apps like gimp that use gtk2 and I doubt they'll ever > switch to gtk3 Gimp is in the process of switching to GTK+ 3, now that the work on changing the internals has reached a nearly complete state. > gtk3 widgets tend to

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Emmanuele Bassi
On 15 September 2017 at 21:13, Clemens Eisserer wrote: > Hi, > > Thanks for the pointer :/ > >> ebassi: LRN: find-as-you-type is gone, and no: it won't come back >> ebassi: As long as we have search embedded into the file chooser >> ebassi: Having two search methods, with conflicting semantics, an

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Clemens Eisserer
Hi, Thanks for the pointer :/ > ebassi: LRN: find-as-you-type is gone, and no: it won't come back > ebassi: As long as we have search embedded into the file chooser > ebassi: Having two search methods, with conflicting semantics, and the same > trigger ("start typing") is not going to work I kno

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Chris Moller
There are some major apps like gimp that use gtk2 and I doubt they'll ever switch to gtk3--gtk3 widgets tend to be a lot bigger than gtk2 widgets, making control-intensive dialogues bigger, taking away space from whatever you're trying to do. I've written a bunch of apps over the last few year

Re: How to get a "traditional" file-chooser

2017-09-15 Thread LRN
On 9/15/2017 9:28 PM, Clemens Eisserer wrote: > I actually sat down and compared GTK2 and GTK3 regarding the file-chooser. > The one and only thing that really bothers me is GTK3 starting a > search immediatly when I start typing a file-name, where I only would > like it to jump to the file/folder

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Michael Torrie
On 09/14/2017 10:56 PM, Daniel Kasak wrote: > Come on. It's troll bait. No I don't think so either. Responses like yours to issues like this are really unhelpful to everyone. > He comes to a gtk+ list, declaring his > preference upfront to not use gtk3 because the "file chooser is > driving me

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Steven Verbeek
You have access to the low level apis of the OS just use those to initiate the file picker. On Sep 15, 2017 15:29, "Clemens Eisserer" wrote: > Hi, > > > Come on. It's troll bait. > Actually it is not. > > > Just wondering: what apps use a file chooser anyway? > Evince, Firefox, Gimp (still GTK2)

Re: How to get a "traditional" file-chooser

2017-09-15 Thread Clemens Eisserer
Hi, > Come on. It's troll bait. Actually it is not. > Just wondering: what apps use a file chooser anyway? Evince, Firefox, Gimp (still GTK2), Eclipse, Geany (still GTK2), ... > He comes to a gtk+ list, declaring his > preference upfront to not use gtk3 because the "file chooser is > driving me

Re: g_signal_emitv -- where is it used in application code?

2017-09-15 Thread Stefan Salewski
On Fri, 2017-09-15 at 13:26 +0100, Emmanuele Bassi wrote: > I'm puzzled by this question. How do you test signal emission *now*? > Actually: how do you even implement it, if you're not already using > g_signal_emitv()? I never needed it! In my C and Ruby applications. And I can not remember that i

Re: g_signal_emitv -- where is it used in application code?

2017-09-15 Thread Emmanuele Bassi
On 15 September 2017 at 13:18, Stefan Salewski wrote: > On Fri, 2017-09-15 at 12:25 +0100, Emmanuele Bassi wrote: >> The g_signal_emitv() function is the vector-based function for >> emitting signals in language bindings. >> >> The variadic argument version is a C convenience function, as >> funct

Re: g_signal_emitv -- where is it used in application code?

2017-09-15 Thread Stefan Salewski
On Fri, 2017-09-15 at 12:25 +0100, Emmanuele Bassi wrote: > The g_signal_emitv() function is the vector-based function for > emitting signals in language bindings. > > The variadic argument version is a C convenience function, as > functions with variadic arguments are not introspectable. > > Thi

Re: g_signal_emitv -- where is it used in application code?

2017-09-15 Thread Emmanuele Bassi
The g_signal_emitv() function is the vector-based function for emitting signals in language bindings. The variadic argument version is a C convenience function, as functions with variadic arguments are not introspectable. This is a typical pattern for any GObject-based library; for every variadic

g_signal_emitv -- where is it used in application code?

2017-09-15 Thread Stefan Salewski
https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-signal-emitv For the most recent issue https://github.com/StefanSalewski/gintro/issues/8 I have absolutely no idea currently. Is g_signal_emitv() generally used in applications code, or is it used for library development (creatio

Re: One more Gobject Introspection issue

2017-09-15 Thread Stefan Salewski
On Fri, 2017-09-15 at 10:28 +0100, Emmanuele Bassi wrote: > All API that takes a GtkIconSize should have a `type int` annotation. Thanks. I learned that already from the reply of Mr. Phil Clayton. Seems that some functions like gtk_toolbar_set_icon_size() do not yet have a `type int` annotation.

Re: One more Gobject Introspection issue

2017-09-15 Thread Emmanuele Bassi
On 14 September 2017 at 21:12, Stefan Salewski wrote: > GtkIconSize type is reported as plain gint, but it is an enum. It's an "extensible" enumeration, like GtkResponseType for GtkDialog: the API accepts an integer, because app and library developers can register their own icon sizes, but GTK+ p

Re: One more Gobject Introspection issue

2017-09-15 Thread Stefan Salewski
On Fri, 2017-09-15 at 09:57 +0100, Phil Clayton wrote: > Have a look at > https://bugzilla.gnome.org/show_bug.cgi?id=601425 Great, thanks. I had looked only into the list of gobject-introspection bugs mentioned at the bottom of this page: https://wiki.gnome.org/action/show/Projects/GObjectIntros

Gobject decorator -> How to deal with properties

2017-09-15 Thread Gonzalo Aguilar Delgado
Hello, I'm writting a decorator pattern for a protocol in Thrift that's based on c_glib. One of the cases I found is that you can have this: // From Thrift code: /*! * Thrift Protocol Decorator instance. */ struct _ThriftProtocolDecorator { ThriftProtocol parent; ThriftProtocol *concr