Re: [Inkscape-devel] Inkscape 0.47pre2
Forgot to reply to all again... anyway, new news is http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.exe with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not the newest, but newer) fixes that problem with them not working as extended input devices.
On Tue, Sep 1, 2009 at 9:49 PM, Chris Morgan <chris.morganiser@...400...>wrote:
On Tue, Sep 1, 2009 at 8:02 AM, Alvin Penner <penner@...1856...> wrote:
Alexandre Prokoudine wrote:
OK, so can we use this build?
I've been using the build : inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-1.exe. and it is working very well for me, thanks Chris!
Good :-)
The only 'issue' I've seen is that it apparently does not include the
Python packages 'PIL' and 'uniconvertor', which I think would normally be present in a Windows installation.
I happened to notice that today before you emailed, looking at it for some PortableApps.com stuff (CommonFiles stuff - a "feasibility study" for a unified Python distribution except for extra libs, for Python apps and apps that use Python, e.g. Blender, Inkscape (both contain), Task Coach, BPBible, others (are written in)). I'd seen PIL in 0.46, and noticed it wasn't there. It has since occurred to me that I have not updated my devlibs bundle (the download contains all the SVN metadata for the repo) as recommended in the Win32Port wiki page, so I'm going to do that now and rebuild it all. I think that that should fix it, and also it'll just make sure everything is up to date. The devlibs bundle I downloaded was at r14, so I'm updating it to the latest, r20.
Sorry about that guys. I plan now on being able to upload Inkscape-0.47pre2-2.exe tomorrow (probably in about 20 hours time).
--
View this message in context: http://www.nabble.com/Inkscape-0.47pre2-tp25110580p25231102.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-- God bless,
Chris Morgan <chris.morganiser@...400...>
I'm good at making two things: mistakes and enemies.
-- Chris Morgan <chris.morganiser@...400...>
I'm good at making two things: mistakes and enemies.
On Wed, 2009-09-02 at 17:26 +1000, Chris Morgan wrote:
Forgot to reply to all again... anyway, new news is http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.exe with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not the newest, but newer) fixes that problem with them not working as extended input devices.
Thank you SO much for doing this Chris... you also saved yourself an email from me asking what the status was. :P
I'm going through and trying to find the win32 tablet bugs and giving the link for the build so we can determine if it's fixed or not.
Cheers, Josh
On Wed, 2009-09-02 at 17:26 +1000, Chris Morgan wrote:
Forgot to reply to all again... anyway, new news is http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.exe with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not the newest, but newer) fixes that problem with them not working as extended input devices.
Chris,
It appears that this fixes the tablet issues on win32, even the bamboo issues which have been a problem for a while. Were the libs done in-place, or did you and Bob officially update the libs for all win32 builders? If it's not official yet, we really need to do this for 0.47 and should push to get it done as soon as possible. Please let me know the status on this and thanks for getting that build made!
Cheers, Josh
I just updated to the ones I should have been using, r20 from inkscape.modevia.org. r14 is what the download was at the time (I guess it's still so), and r16 included new GTK libraries (even if they're now out of date). The instructions on the Win32Port page said to update, but I forgot to. So "I apologise for any inconvenince caused", but it's fixed now :-)
I'll try updating the GTK once more after this, based on r20 instead of r14, to see if it's any better. But we should be able to release 0.47 for Windows with the *real* current binaries and have it work now, which is good.
On Thu, Sep 3, 2009 at 11:33 AM, Joshua A. Andler <scislac@...400...> wrote:
On Wed, 2009-09-02 at 17:26 +1000, Chris Morgan wrote:
Forgot to reply to all again... anyway, new news is http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.exe with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not the newest, but newer) fixes that problem with them not working as extended input devices.
Chris,
It appears that this fixes the tablet issues on win32, even the bamboo issues which have been a problem for a while. Were the libs done in-place, or did you and Bob officially update the libs for all win32 builders? If it's not official yet, we really need to do this for 0.47 and should push to get it done as soon as possible. Please let me know the status on this and thanks for getting that build made!
Cheers, Josh
-- Chris Morgan <chris.morganiser@...400...>
I'm good at making two things: mistakes and enemies.
-----Original Message----- From: Joshua A. Andler [mailto:scislac@...400...] Sent: 03 September, 2009 08:33 To: Chris Morgan Cc: Inkscape Developers' Mailing List; Bob Jamison Subject: [Inkscape-devel] Win32 libs update request - was Re: Inkscape 0.47pre2
On Wed, 2009-09-02 at 17:26 +1000, Chris Morgan wrote:
Forgot to reply to all again... anyway, new news is http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.exe with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not the newest, but newer) fixes that problem with them not working as extended input devices.
Chris,
It appears that this fixes the tablet issues on win32, even the bamboo issues which have been a problem for a while. Were the libs done in-place, or did you and Bob officially update the libs for all win32 builders? If it's not official yet, we really need to do this for 0.47 and should push to get it done as soon as possible. Please let me know the status on this and thanks for getting that build made!
Cheers, Josh
It has been much improved, but bug https://bugs.launchpad.net/bugs/284546 is still there, though it does not appear quite as easy as before.
Couldn't the THROW_CONTINUITYERROR at line 355 in src\2geom\path.cpp be commented out, as suggested long time ago. That would help a lot.
Thanks for the effort Chris.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30- Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-----Original Message----- From: Preben Soeberg [mailto:prsodk@...400...] Sent: Thursday, September 03, 2009 21:04 To: 'Joshua A. Andler' Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs update request - was Re: Inkscape0.47pre2
-----Original Message----- From: Joshua A. Andler [mailto:scislac@...400...] Sent: 03 September, 2009 08:33 To: Chris Morgan Cc: Inkscape Developers' Mailing List; Bob Jamison Subject: [Inkscape-devel] Win32 libs update request - was
Re: Inkscape
0.47pre2
On Wed, 2009-09-02 at 17:26 +1000, Chris Morgan wrote:
Forgot to reply to all again... anyway, new news is
http://inkscape.chrismorgan.info/win32-builds/Inkscape-0.47pre2-2.ex
e with the updated devlibs. I'd especially like this tested with graphics tablets to see if the updated GTK version (not
the newest,
but newer) fixes that problem with them not working as extended input devices.
Chris,
It appears that this fixes the tablet issues on win32, even
the bamboo
issues which have been a problem for a while. Were the libs done in-place, or did you and Bob officially update the libs for
all win32
builders? If it's not official yet, we really need to do
this for 0.47
and should push to get it done as soon as possible. Please
let me know
the status on this and thanks for getting that build made!
Cheers, Josh
It has been much improved, but bug https://bugs.launchpad.net/bugs/284546 is still there, though it does not appear quite as easy as before.
Couldn't the THROW_CONTINUITYERROR at line 355 in src\2geom\path.cpp be commented out, as suggested long time ago. That would help a lot.
We should definitely not remove THROW_CONTINUITYERROR ! It means there is a real problem that Inkscape/2geom should not ignore. I think what causes the problem in this case is adding a line segment with 'invalid' points (like infinity). Perhaps adding a simple check for that in the callygr tool will fix this issue.
Ciao, Johan
On Fri, Sep 4, 2009 at 7:40 AM, <J.B.C.Engelen@...1578...> wrote:
We should definitely not remove THROW_CONTINUITYERROR ! It means there is a real problem that Inkscape/2geom should not ignore. I think what causes the problem in this case is adding a line segment with 'invalid' points (like infinity). Perhaps adding a simple check for that in the callygr tool will fix this issue.
Does this exception lead to crashing? If yes we must definitely disable it for the release, and possibly reenable afterwards (if there's interest in fixing it properly). End users should not be forced to help us debug our bugs if there's any chance of crashing.
-----Original Message----- From: bulia byak [mailto:buliabyak@...400...] Sent: 05 September, 2009 04:13 To: J.B.C.Engelen@...1578... Cc: prsodk@...400...; scislac@...400...; inkscape- devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs update request - was Re: Inkscape0.47pre2
On Fri, Sep 4, 2009 at 7:40 AM, <J.B.C.Engelen@...1578...> wrote:
We should definitely not remove THROW_CONTINUITYERROR ! It means there is a real problem that Inkscape/2geom should not ignore. I think what causes the problem in this case is adding a line segment with 'invalid' points (like infinity). Perhaps adding a simple check for that in the callygr tool will fix this issue.
Does this exception lead to crashing? If yes we must definitely disable it for the release, and possibly reenable afterwards (if there's interest in fixing it properly). End users should not be forced to help us debug our bugs if there's any chance of crashing.
Yes, it causes crashes, and it makes the calligraphic tracing feature virtually unusable in Windows (when using the Wacom).
I should explain more clearly.
I agree that end users should not suffer a crash for us to find bugs. However, this exception is a low level check to see if the path is still a valid path. It's like the many other assertions Inkscape contains. I have argued against these things in the past, but I don't think we should remove/disable this one. It is actually used by Inkscape as well (I hate "g_assert" and love "throw", because it's possible to resolve a throw); some LPE's give invalid paths, and Inkscape notices this and stops LPE execution. Removing THROW_CONTINUITYERROR will mean that those LPEs will give faulty paths, and Inkscape won't notice it, giving faulty SVGs i think.
(otoh, I introduced these macros in 2geom to easily disable all of the exception throwing for a release........)
Cheers, Johan
-----Original Message----- From: Preben Soeberg [mailto:prsodk@...400...] Sent: zaterdag 5 september 2009 5:29 To: 'bulia byak' Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs update request - was Re:Inkscape0.47pre2
-----Original Message----- From: bulia byak [mailto:buliabyak@...400...] Sent: 05 September, 2009 04:13 To: J.B.C.Engelen@...1578... Cc: prsodk@...400...; scislac@...400...; inkscape- devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs update request - was Re: Inkscape0.47pre2
On Fri, Sep 4, 2009 at 7:40 AM,
<J.B.C.Engelen@...1578...> wrote:
We should definitely not remove THROW_CONTINUITYERROR ! It means there is a real problem that Inkscape/2geom should not ignore. I think what causes the problem in this case is adding a line segment with 'invalid' points (like infinity). Perhaps adding a simple check for that in the callygr tool will fix this issue.
Does this exception lead to crashing? If yes we must definitely disable it for the release, and possibly reenable afterwards (if there's interest in fixing it properly). End users should not be forced to help us debug our bugs if there's any chance of crashing.
Yes, it causes crashes, and it makes the calligraphic tracing feature virtually unusable in Windows (when using the Wacom).
On Sat, Sep 5, 2009 at 6:49 AM, <J.B.C.Engelen@...1578...> wrote:
I agree that end users should not suffer a crash for us to find bugs. However, this exception is a low level check to see if the path is still a valid path.
This late in the release, I'm afraid we have no other choice. Is it crashing? Yes. Can we fix it "properly"? No. Can we fix it at least somehow? Yes, by removing the assert, or at least making it non-crashing. I think the choice is obvious :)
It's like the many other assertions Inkscape contains.
Except that those other asserts stand on guard but never fire, in normal use. This one fires (and kills).
By the way I never had crashes from this assert on Linux, even though I also use Wacom with Calligraphic pen extensively. So this seems to be a Windows-only bug.
bulia byak wrote:
By the way I never had crashes from this assert on Linux, even though I also use Wacom with Calligraphic pen extensively. So this seems to be a Windows-only bug.
Unfortunately - no. I am the submitter of original bug report and it still crashes for me. Even worse, it locks my X server completely so I have to switch to VT (ctrl+alt+F1) and kill inkscape from there.
If I can help anyhow, I'll do it... Just say it.
Vlada
participants (6)
-
unknown＠example.com -
bulia byak -
Chris Morgan -
Joshua A. Andler -
Preben Soeberg -
Vladimir Savic