Ignore my last email, John. I managed to find a non-gtkmm window where I was
able to reproduce the problem - so it's definitely a GTK+ issue, like you said.
I came across this entry in bugzilla:-
https://bugzilla.gnome.org/show_bug.cgi?id=646930
which is the same problem AFAICT. This seems l
Hi John (jcupitt)
Out of interest - does your app use gtkmm and if not, do you have an earlier
version available? One built against GTK+ 2.20 would be ideal.
The reason I'm asking is that our particular app uses gtkmm as a layer over
gtk+. I've come to realise this afternoon that the problem
On 6 Mar 2012, at 12:37, jcup...@gmail.com wrote:
>
> Yes, this (and many other annoying bugs) were fixed for 2.24. You
> should see good improvements to copy/paste, drag/drop and filename
> encoding support as well. It might even be a bit quicker.
>
> I've just rebuilt my program against 2.24 i
Hi John,
On 6 March 2012 09:38, John Emmas wrote:
> We're using GTK+ v2.20.0 which was current at that time. The Windows version
> has a peculiar problem
>
> The problem affects any "scrollable / draggable" object but the easiest
> example to explain is probably a scroll bar. Let's say I left
Hello. For the past couple of years we've been using GTK+/Glib etc for
building a cross platform app. We're using GTK+ v2.20.0 which was current at
that time. The Windows version has a peculiar problem and I just wondered if
either (a) it's fixed in a more recent version - or (b) if anyone ca
