I just noticed that in Oneiric that my tablet isn't doing it's thing even with everything switched on.
Is there still a bug in inkscape trunk over the pressure?
This is what I dug up: http://osdir.com/ml/ubuntu-bugs/2011-11/msg06429.html
It looks like it might be a gtk bug? If so, what needs to happen to fix it?
Martin,
On Sun, Dec 18, 2011 at 2:33 AM, Martin Owens wrote:
I just noticed that in Oneiric that my tablet isn't doing it's thing even with everything switched on.
1. Your "description" doesn't shed a single ray of light on the actal issue you are talking about :)
2. Up to date GTK+2 is known to be broken beyond repair regarding advanced input devices. And it's not going to be fixed.
Alexandre Prokoudine http://libregraphicsworld.org
---- Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Sun, Dec 18, 2011 at 2:33 AM, Martin Owens wrote:
I just noticed that in Oneiric that my tablet isn't doing it's thing even with everything switched on.
- Your "description" doesn't shed a single ray of light on the actal
issue you are talking about :)
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Impressively pessimistic in so few words... Does this mean we have to get a move on switching to GTK+3?
(I was very disappointed upon installing my tablet that pressure sensitivity does not work in trunk :(
Ciao, Johan
On Sat, Dec 17, 2011 at 6:13 PM, <jbc.engelen@...2592...> wrote:
---- Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Sun, Dec 18, 2011 at 2:33 AM, Martin Owens wrote:
I just noticed that in Oneiric that my tablet isn't doing it's thing even with everything switched on.
- Your "description" doesn't shed a single ray of light on the actal
issue you are talking about :)
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Impressively pessimistic in so few words... Does this mean we have to get a move on switching to GTK+3?
So very true... Alexandre has a knack for decimating one's hopes and dreams with such grace and brilliance. :) The "best" option is really for someone with Windows to dig around for set of win GTK+ libs that doesn't have the security vulnerability present in the last one we shipped which still supports tablets correctly.
I say best because I don't know the status of the GTK3 advanced input devices support and because even if it were a better option, a number of our linux users will take serious issue with bumping the lib requirements that much. I hate to be a jerk, but this doesn't bother me all that much. I certainly won't lose any sleep over users who don't want to upgrade not being able to have the latest and greatest Inkscape. Before anyone makes an LTS/Enterprise argument, typically they want all software locked to the shipped versions, so I'm not buying it.
(I was very disappointed upon installing my tablet that pressure sensitivity
does not work in trunk :(
You and countless other Windows users...
Cheers, Josh
On Dec 17, 2011, at 7:39 PM, Josh Andler wrote:
I say best because I don't know the status of the GTK3 advanced input devices support and because even if it were a better option, a number of our linux users will take serious issue with bumping the lib requirements that much. I hate to be a jerk, but this doesn't bother me all that much. I certainly won't lose any sleep over users who don't want to upgrade not being able to have the latest and greatest Inkscape. Before anyone makes an LTS/Enterprise argument, typically they want all software locked to the shipped versions, so I'm not buying it.
Unfortunately at the moment it's the OS X users who'd probably suffer the most from a GTK+3 transition.
But the good news is that in the last month or so things have finally picked back up on that front.
However... given many of the other things we have to clean up first, by the time we're ready to flip the switch we're probably looking at a good transition time.
On Sat, Dec 17, 2011 at 6:13 PM, <jbc.engelen@...2592...> wrote:
---- Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Impressively pessimistic in so few words... Does this mean we have to get a move on switching to GTK+3?
Just a side note, Alexandre's official title at Libre Graphics World http://libregraphicsworld.org/ (subtle, eh?) should be "Giver of Hope, Destroyer of Dreams". :D
Johan, as an aside, you may want to check out GIMP, MyPaint, or Inkscape 0.48.1 on windows (I don't recall if Alchemy has advanced tablet support) to possibly have some fun with your tablet.
Cheers, Josh
P.S. That wasn't a shameless plug, if you're into floss creative software (visual, auditory, etc), it's a really good resource to know what's going on.
On Dec 17, 2011, at 3:11 PM, Alexandre Prokoudine wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Can you give some details on this?
I've been using a few different Wacom's on GTK2 many places,
Are you perhaps talking about things like multi-touch?
On Sat, Dec 17, 2011 at 8:36 PM, Jon Cruz <jon@...18...> wrote:
On Dec 17, 2011, at 3:11 PM, Alexandre Prokoudine wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
I've been using a few different Wacom's on GTK2 many places,
Are you perhaps talking about things like multi-touch?
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
Cheers, Josh
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
Ubuntu 10.10 = happy happy.
Intuos4
(Hmmm... this was supposed to go out last night, but my mail got stuck. Let's see if it works now)
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy
(last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
Ubuntu 10.10 = happy happy.
All Windows users are currently disenfranchised as are Linux users using any distro releases from this year and moving forward.
Cheers, Josh
On 18/12/11 21:56, Josh Andler wrote:
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
Not really: MacPorts doesn't allow to freely choose a version of a port, it always installs the latest version from the Portfile.
Currently, MacPorts has the latest release of Gtk2 (2.24.8): https://trac.macports.org/browser/trunk/dports/gnome/gtk2/Portfile - the upgrade from 2.22.1 to 2.24.3 happened 9 months ago, - the upgrade from 2.20.1 to 2.22.0 was 14 months ago
~suv
On Sun, Dec 18, 2011 at 1:15 PM, ~suv <suv-sf@...58...> wrote:
On 18/12/11 21:56, Josh Andler wrote:
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
Not really: MacPorts doesn't allow to freely choose a version of a port, it always installs the latest version from the Portfile.
Ahhh, I was probably confused by when the user I asked about needed to update XQuartz... I thought that was supplied by MacPorts, after looking back at the link, obviously it's not. Just so I know, is MacPorts somewhat like a package management system since it always installs the latest and greatest then?
Currently, MacPorts has the latest release of Gtk2 (2.24.8): https://trac.macports.org/browser/trunk/dports/gnome/gtk2/Portfile
- the upgrade from 2.22.1 to 2.24.3 happened 9 months ago,
- the upgrade from 2.20.1 to 2.22.0 was 14 months ago
Good to know. So, it forces the upgrade then or can you choose to not upgrade?
Cheers, Josh
On 19/12/11 00:15, Josh Andler wrote:
On Sun, Dec 18, 2011 at 1:15 PM, ~suv <suv-sf@...58...> wrote:
On 18/12/11 21:56, Josh Andler wrote:
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
Not really: MacPorts doesn't allow to freely choose a version of a port, it always installs the latest version from the Portfile.
Ahhh, I was probably confused by when the user I asked about needed to update XQuartz... I thought that was supplied by MacPorts, after looking back at the link, obviously it's not. Just so I know, is MacPorts somewhat like a package management system since it always installs the latest and greatest then?
Yes, like a package manager it helps to install and upgrade packages (ports) and handles the dependencies. It differs though in that it does not install (binary) packages, but builds everything from the sources.
(There is work-in-progress to provide binary packages, but for now those are limited to Snow Leopard, only few in numbers and only with default variants).
Currently, MacPorts has the latest release of Gtk2 (2.24.8): https://trac.macports.org/browser/trunk/dports/gnome/gtk2/Portfile
- the upgrade from 2.22.1 to 2.24.3 happened 9 months ago,
- the upgrade from 2.20.1 to 2.22.0 was 14 months ago
Good to know. So, it forces the upgrade then or can you choose to not upgrade?
It forces the upgrade: default usage is upgrading all outdated ports (i.e. all ports for which the portfile in the shared repository was updated to install a newer version).
You can manually exclude individual ports from upgrading, but this is not recommended (unless really needed e.g. because of a bug) and has to be done every time when upgrading outdated ports after the database is checked for changes. Alternatively you can maintain a local portfile repository to override the shared one and thus keep certain ports at older versions. This sooner or later can get you into dependency hell ;)
~suv
On Dec 18, 2011, at 12:56 PM, Josh Andler wrote:
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
There are only limited choices, and not all will work .
Ubuntu 10.10 = happy happy.
All Windows users are currently disenfranchised as are Linux users using any distro releases from this year and moving forward.
Also some distros have randomly disenfranchised many Linux users already. :-)
The good news is that once our codebase is gtk 3.x compatible we can get the Windows people covered while still going with GTK 2 compatibility for those holding back from linuxy upgrades. With the odd push for forcing Unity, Ubuntu is actually getting quite a few people to hold back.
And other good news is that many of the rough edges on GTK3 are getting addressed by now, so transitioning is much more feasible.
On 18/12/11 18:36, Jon Cruz wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
Ubuntu 10.10 = happy happy.
Intuos4
Another "happy, happy" here: Confirmed with Inkscape 0.48.2 on OS X 10.7.2 Lion
Hardware: - Wacom Bamboo Pen&Touch (CTH-470) Software: - Inkscape: official package for 0.48.2 (built with GTK+ 2.24) - X11/Xquartz 2.6.3 (xorg-server 1.10.3)
Pressure sensitivity works fine e.g. with the calligraphy tool to adjust the width of the stroke.
(Note: these are initial tests with newly acquired hardware ;) )
~suv
On 19/12/2011 12:02, ~suv wrote:
On 18/12/11 18:36, Jon Cruz wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
Ubuntu 10.10 = happy happy.
Intuos4
Another "happy, happy" here: Confirmed with Inkscape 0.48.2 on OS X 10.7.2 Lion
Hardware:
- Wacom Bamboo Pen&Touch (CTH-470)
Software:
- Inkscape: official package for 0.48.2 (built with GTK+ 2.24)
- X11/Xquartz 2.6.3 (xorg-server 1.10.3)
Pressure sensitivity works fine e.g. with the calligraphy tool to adjust the width of the stroke.
(Note: these are initial tests with newly acquired hardware ;) )
2) Inkscape trunk r10785 (gtk2/x11 2.24.4) built and bundled on Mac OS X 10.5.8 Leopard as 32bit app, tested on OS X 10.7.2 Lion:
pressure sensitivity for calligraphy and tweak tool ok
3) Inkscape trunk r10785 (gtk2/quartz 2.24.8) built and bundled on Mac OS X 10.5.8 Leopard as 32bit app, tested on OS X 10.7.2 Lion:
The tablet is not even recognized (not listed under 'Files > Input Devices') [1], trying to test the pen in the 'Hardware' tab of the 'Input Devices' dialog apparently crashed the Wacom driver (-> tablet input broken for all apps and the desktop, restored after logging out and back in).
Once I have working build environments on Lion (hopefully next week), I can do more tests with trunk (gtk2/x11 as well as gtk2/quartz builds).
~suv
[1] this is not unexpected: the same was reported about MyPaint: the Mac installer for 1.0 is based on gtk2/quartz 2.24.8 as well, and does not detect any extended input devices: https://bugzilla.gnome.org/show_bug.cgi?id=663990
On Dec 20, 2011, at 12:14 PM, ~suv wrote:
- Inkscape trunk r10785 (gtk2/quartz 2.24.8)
built and bundled on Mac OS X 10.5.8 Leopard as 32bit app, tested on OS X 10.7.2 Lion:
The tablet is not even recognized (not listed under 'Files > Input Devices') [1], trying to test the pen in the 'Hardware' tab of the 'Input Devices' dialog apparently crashed the Wacom driver (-> tablet input broken for all apps and the desktop, restored after logging out and back in).
I'm not surprised at this.
Before the native GTK progress on OSX stalled out I had gotten about halfway through adding tablet support. Hopefully with the momentum it just gained the other month we'll be able to clean it up and get it going.
On Sun, Dec 18, 2011 at 8:36 AM, Jon Cruz wrote:
On Dec 17, 2011, at 3:11 PM, Alexandre Prokoudine wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Can you give some details on this?
I've been using a few different Wacom's on GTK2 many places,
Are you perhaps talking about things like multi-touch?
Nope, I really mean graphic tablets like Wacom's. Their support in up to date GTK+ is ranging from "oh, it works" to "what the hell has happened to pressure sensitivity?". I'm on Ubuntu 11.10 right now, and pressure sensitivity simply doesn't work for my aging Graphire3. If you want technical details, ask Michael Natterer.
AFAIK, it broke around 2.22 or 2.24. E.g. MyPaint is shipped on Windows with 2.16 or something, which is why it works, so does GIMP 2.6. But the current unstable version of GIMP relies on most recent GTK+ for a number of reasons, hence 2.8 is going to be shipped with broken tablets support despite of multiple improvements in brush dynamics.
Simply put, whenever you build an app, linking it to up to date GTK+2, you break advanced input devices support. This, I think, is a good reason to be careful when packaging Inkscape.
As for GTK+3, it doesn't have that problem, which is why we shall probably not wait for GEGL integration to finish for 3.0. It really sucks to have advanced brush dynamics (and 2.8 is really awesome there) and not be able to use it to its full potential.
Alexandre Prokoudine http://libregraphicsworld.org
On Sun, Dec 18, 2011 at 11:54 AM, Alexandre Prokoudine wrote:
Simply put, whenever you build an app, linking it to up to date GTK+2, you break advanced input devices support. This, I think, is a good reason to be careful when packaging Inkscape.
As for GTK+3, it doesn't have that problem, which is why we shall probably not wait for GEGL integration to finish for 3.0. It really sucks to have advanced brush dynamics (and 2.8 is really awesome there) and not be able to use it to its full potential.
Speaking of which, linuxwacom folks have just released first version of libwacom.
"libwacom is a library to identify wacom tablets and their model-specific features. It provides easy access to information such as "is this a built-in on-screen tablet", "what is the size of this model", etc."
Alexandre Prokoudine http://libregraphicsworld.org
On Sun, 2011-12-18 at 03:11 +0400, Alexandre Prokoudine wrote:
- Your "description" doesn't shed a single ray of light on the actal
issue you are talking about :)
It doesn't work. Your response doesn't shed a single ray of light on what else you might need. Although I contest that I linked to bug reports and specified versions it doesn't work in and the suspected issue. It's not like I didn't do due diligence testing multiple versions and doing google searches, so spare me your unsocial attitude problem.
Interestingly the tablet works in Gimp 2.6, but fails in Inkscape. So I blame the Inkscape developers for delivering a broken release. I'd have been kinder, but you get what you give.
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Then why are you using it? Did it break on you? then set a maximum version in the packaging so we have to use a lower version to get a working Inkscape. You shouldn't accept such nasty regressions and if you have to, ship the bastard library internally. Surely the inkscape project has smarter people than: 'It doesn't work so we gave up'
Martin,
On Mon, Dec 19, 2011 at 4:55 PM, Martin Owens wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Then why are you using it? Did it break on you? then set a maximum version in the packaging so we have to use a lower version to get a working Inkscape. You shouldn't accept such nasty regressions and if you have to, ship the bastard library internally. Surely the inkscape project has smarter people than: 'It doesn't work so we gave up'
Martin,
If I didn't know you from other FLOSS projects I'd think that this is some sort of horrible anti-floss trolling :)
As far as I can tell, when 0.48.0 was out, the issue didn't exist. That is wasn't taken care of later is a whole different matter. We can burst out with rage all we like, but I for one would rather see this thread go back to discussing how we can fix the issue, not how we can punch each other in the face.
Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
Alexandre Prokoudine http://libregraphicsworld.org
On 19 December 2011 18:02, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
Yeah, I'm not so keen on this either. gdl is only a little library, with just a couple of local changes in our fork, but we've managed to accumulate a pretty big delta against upstream over time. GTK+ is a much bigger library, so it'll be very painful to maintain it. Also, setting a maximum version of a library seems a bit risky - how do we deal with important upstream security fixes, for example?
If this is definitely a known gtk+ issue, do we have an upstream bug we can track? Any idea if there will ever be a fix backported to a release of gtk+ 2, or is this really a case of Inkscape being broken until we reach gtk+ 3 compliance?
AV
On Mon, Dec 19, 2011 at 10:25 PM, Alex Valavanis wrote:
On 19 December 2011 18:02, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
Yeah, I'm not so keen on this either. gdl is only a little library, with just a couple of local changes in our fork, but we've managed to accumulate a pretty big delta against upstream over time. GTK+ is a much bigger library, so it'll be very painful to maintain it. Also, setting a maximum version of a library seems a bit risky - how do we deal with important upstream security fixes, for example?
If this is definitely a known gtk+ issue, do we have an upstream bug we can track? Any idea if there will ever be a fix backported to a release of gtk+ 2, or is this really a case of Inkscape being broken until we reach gtk+ 3 compliance?
I dare say https://bugzilla.gnome.org/show_bug.cgi?id=653437 is the one
Alexandre Prokoudine http://libregraphicsworld.org
On 19 December 2011 18:31, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
I dare say https://bugzilla.gnome.org/show_bug.cgi?id=653437 is the one
Thanks! Do you think it's worth linking to bug #845354?.. or is that possibly a different issue?
https://bugs.launchpad.net/inkscape/+bug/845354
AV
On Mon, Dec 19, 2011 at 10:53 PM, Alex Valavanis wrote:
On 19 December 2011 18:31, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
I dare say https://bugzilla.gnome.org/show_bug.cgi?id=653437 is the one
Thanks! Do you think it's worth linking to bug #845354?.. or is that possibly a different issue?
I'm not quite sure. I've already made some assumptions in this thread and look what it's led to :) I'd rather leave it to people who know things and go places.
Alexandre Prokoudine http://libregraphicsworld.org
On 12/19/2011 07:31 PM, Alexandre Prokoudine wrote:
If this is definitely a known gtk+ issue, do we have an upstream bug
we can track? Any idea if there will ever be a fix backported to a release of gtk+ 2, or is this really a case of Inkscape being broken until we reach gtk+ 3 compliance?
I dare sayhttps://bugzilla.gnome.org/show_bug.cgi?id=653437 is the one
A), out of range coordinates, is what I experienced with a Krita beta on Ubuntu 11.10. Apparently the same thing that makes Krita crash causes random straight lines to towards the canvas edge in GIMP, which led me to https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/863154
I don't tend to use the tablet with Inkscape, but would have tested it now ... if my tablet didn't stop working altogether once again.
On Mon, Dec 19, 2011 at 10:02 AM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Mon, Dec 19, 2011 at 4:55 PM, Martin Owens wrote: Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
After seeing how difficult it has been to try and get our internal copies of libcroco, libgdl, and lib2geom out of trunk, there's no way in good conscience that I could say it would be a good idea to bring an instantly stagnant copy of gtk in-tree.
As evil as it is to say "screw our tablet users", I'd say we're screwing users more by not having someone reach out to fix the issues upstream. It would benefit far more than our users directly and is the "right" way to go about it. That said, we really only have one developer who really ever delves into input devices, and that is something that slowly improves (if at all) between releases.
I think it's the wrong solution, that's my .02
Cheers, Josh
Thanks Alexandre,
I understand your scary concerns, I have them too.
So the release was caught unawares by an external dependency, bit of a bastard. I wonder how Gimp is still working, surely that's Gtk too?
Martin,
On Mon, 2011-12-19 at 22:02 +0400, Alexandre Prokoudine wrote:
If I didn't know you from other FLOSS projects I'd think that this is some sort of horrible anti-floss trolling :)
As far as I can tell, when 0.48.0 was out, the issue didn't exist. That is wasn't taken care of later is a whole different matter. We can burst out with rage all we like, but I for one would rather see this thread go back to discussing how we can fix the issue, not how we can punch each other in the face.
Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
On 19-12-2011 13:55, Martin Owens wrote:
On Sun, 2011-12-18 at 03:11 +0400, Alexandre Prokoudine wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Then why are you using it? Did it break on you? then set a maximum version in the packaging so we have to use a lower version to get a working Inkscape.
Josh says that we upgraded our devlibs with a newer GTK to address a security issue. Perhaps there is a version that is new enough to not have the security issue, but old enough to have working tablets? (this is about Inkscape on Windows of course)
Cheers, Johan
On Mon, Dec 19, 2011 at 1:38 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
On 19-12-2011 13:55, Martin Owens wrote:
On Sun, 2011-12-18 at 03:11 +0400, Alexandre Prokoudine wrote:
- Up to date GTK+2 is known to be broken beyond repair regarding
advanced input devices. And it's not going to be fixed.
Then why are you using it? Did it break on you? then set a maximum version in the packaging so we have to use a lower version to get a working Inkscape.
Inkscape (mostly) works fine, it's tablet support that doesn't. Last time I checked, distros didn't tend to ship older versions of libs than what they supply by default. What happens to users who like up-to-date distros? I just checked in Synaptic and I can't force an earlier version of GTK2 than what Ubuntu supplies. I'd rather have a mostly working Inkscape than no Inkscape at all personally.
Josh says that we upgraded our devlibs with a newer GTK to address a security issue. Perhaps there is a version that is new enough to not have the security issue, but old enough to have working tablets? (this is about Inkscape on Windows of course)
We can control it pretty easily on the win32 side only, and I think we should. This is just where we need a brave win32 developer to explore more deeply.
Cheers, Josh
participants (9)
-
unknown＠example.com -
Alex Valavanis -
Alexandre Prokoudine -
Johan Engelen -
Jon Cruz -
Josh Andler -
Martin Owens -
Thorsten Wilms -
~suv