Re: GTK3 - GtkExpander problem, bug ?

Hi Sébastien, An out of sync reply. I must have accidently deleted your last response after I read it. Also I didn't notice there were two mailing lists referenced. Probably just need the app dev list. It looks like it is a bug that has been recently introduced. If I test, test.c with

Re: First deprecate APIs and then remove them in the next major version

On Thu, Dec 14, 2017 at 08:34:51PM +, Emmanuele Bassi wrote: > On 14 December 2017 at 18:42, Sébastien Wilmet wrote: > > A recent example: > > https://git.gnome.org/browse/gtk+/commit/?id=2d5c82b4ecbe6ff534a1b9476080e409742daa39 > > "gtk: Remove GtkClipboard" > > > > The

Re: First deprecate APIs and then remove them in the next major version

On 14 December 2017 at 18:42, Sébastien Wilmet wrote: > On Wed, Dec 13, 2017 at 04:55:41PM +, 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: >

Re: First deprecate APIs and then remove them in the next major version

On Thu, Dec 14, 2017 at 08:02:56PM +0100, Bastien Nocera wrote: > On Thu, 2017-12-14 at 19:56 +0100, Sébastien Wilmet wrote: > > > > > With "soft API breaks" (i.e. just removing an API that was deprecated > > in > > a previous major version), I think this would improve a lot the > > situation

Re: GTK3 - GtkExpander problem, bug ?

Hi Sébastien, If I try some test code... it should work. The code uses a grid instead of a fixed container. Is this similar to what you have tried? Eric /* gcc -Wall buttons1.c -o buttons1 `pkg-config --cflags --libs gtk+-3.0` Tested with GTK3.18 on Ubuntu16.04 */ #include static

Re: GTK3 - GtkExpander problem, bug ?

Hi Sébastien, If I try some test code... it should work. The code uses a grid instead of a fixed container. Is this similar to what you have tried? Eric /* gcc -Wall buttons1.c -o buttons1 `pkg-config --cflags --libs gtk+-3.0` Tested with GTK3.18 on Ubuntu16.04 */ #include static

Re: First deprecate APIs and then remove them in the next major version

On Thu, 2017-12-14 at 19:56 +0100, Sébastien Wilmet wrote: > > With "soft API breaks" (i.e. just removing an API that was deprecated > in > a previous major version), I think this would improve a lot the > situation and would avoid to repeat the same problem as GTK+ 2 -> 3. It already exists.

Re: First deprecate APIs and then remove them in the next major version

On Wed, Dec 13, 2017 at 03:08:46PM -0800, Christian Hergert wrote: > On 12/13/2017 04:05 AM, Sébastien Wilmet wrote: > > Can I remind you that most of the biggest GTK+ apps are still using > > GTK+ 2? MonoDevelop, GIMP, Ardour, … > > MonoDevelop is still Gtk2 because Novell/Xamarin/Unity3d

Re: First deprecate APIs and then remove them in the next major version

On Wed, Dec 13, 2017 at 04:55:41PM +, 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.gnome.org/browse/gtk+/commit/?id=2d5c82b4ecbe6ff534a1b9476080e409742daa39 "gtk: Remove GtkClipboard"

Re: GTK3 - GtkExpander problem, bug ?

Hello Sébastien, attaching images isn't allowed on here. Have you created a minimal working example that reproduces the bug? Otherwise it'll be hard to help you. Cheers, Tilo ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org

GTK3 - GtkExpander problem, bug ?

Dear all thanks in advance for reading this, I wrote a piece of code in GTK3, and I might have found an issue with the GtkExpander widget, shorter than a long text explanation, I attach to this email a screen capture from a window from my program. This window contains a bunch of GtkExpander,