POV-Ray export patch.
Hi,
I just filed a bug report for POV-Ray export which is broken in 0.47pre4. It appears to have been broken by a move to lib2geom where the path vector includes an extra closing segment even if the path is already closed (see 2geom/path.h). This resulted in extra lines being written out. In addition, there was a problem that existed in 0.46 where paths created by Text->Path may not have their last point exactly on top of the first point (differing sometimes by 0.0002 px). In this case, POV-Ray considers the path open and skips it.
I've attached a patch to the bug report that fixes both problems. I know this is late in the 0.47 release process but as it stands, export to .pov format is useless (POV-Ray fails to process the .pov file due to the extra badly-formatted lines). The patch only effects pov-out.cpp which is used only by POV-Ray export so it shouldn't break anything.
The bug URL is: https://bugs.launchpad.net/inkscape/+bug/451588
Tav
Tav,
That looks good.
Does anyone know if the JavaFX export is similarly broken? The output code is very similar.
Bob
On 10/14/2009 3:23 PM, Tavmjong Bah wrote:
Hi,
I just filed a bug report for POV-Ray export which is broken in 0.47pre4. It appears to have been broken by a move to lib2geom where the path vector includes an extra closing segment even if the path is already closed (see 2geom/path.h). This resulted in extra lines being written out. In addition, there was a problem that existed in 0.46 where paths created by Text->Path may not have their last point exactly on top of the first point (differing sometimes by 0.0002 px). In this case, POV-Ray considers the path open and skips it.
I've attached a patch to the bug report that fixes both problems. I know this is late in the 0.47 release process but as it stands, export to .pov format is useless (POV-Ray fails to process the .pov file due to the extra badly-formatted lines). The patch only effects pov-out.cpp which is used only by POV-Ray export so it shouldn't break anything.
The bug URL is: https://bugs.launchpad.net/inkscape/+bug/451588
Tav
For anyone working on this, please take a look at the comment I added to the bugreport (https://bugs.launchpad.net/inkscape/+bug/451588). Not saying the code is wrong, it's just a bit more complicated than it could be.
In any case, thanks for fixing the stuff I broke. Sorry for that :-(
Ciao, Johan
-----Original Message----- From: Bob Jamison [mailto:ishmalius@...400...] Sent: woensdag 14 oktober 2009 23:42 To: Tavmjong Bah; inkscape Subject: Re: [Inkscape-devel] POV-Ray export patch.
Tav,
That looks good.
Does anyone know if the JavaFX export is similarly broken? The output code is very similar.
Bob
On 10/14/2009 3:23 PM, Tavmjong Bah wrote:
Hi,
I just filed a bug report for POV-Ray export which is broken in 0.47pre4. It appears to have been broken by a move to
lib2geom where
the path vector includes an extra closing segment even if
the path is
already closed (see 2geom/path.h). This resulted in extra
lines being
written out. In addition, there was a problem that existed in 0.46 where paths created by Text->Path may not have their last point exactly on top of the first point (differing sometimes by
0.0002 px).
In this case, POV-Ray considers the path open and skips it.
I've attached a patch to the bug report that fixes both
problems. I
know this is late in the 0.47 release process but as it
stands, export
to .pov format is useless (POV-Ray fails to process the
.pov file due
to the extra badly-formatted lines). The patch only effects pov-out.cpp which is used only by POV-Ray export so it
shouldn't break anything.
The bug URL is: https://bugs.launchpad.net/inkscape/+bug/451588
Tav
Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Oct 14, 2009, at 2:41 PM, Bob Jamison wrote:
Does anyone know if the JavaFX export is similarly broken? The output code is very similar.
I've been trying to get some actual JavaFX users to check things, but they seem very non-responsive (including Sun's official JavaFX contacts, etc)
So given the lack of any response at all from the JavaFX community, I feel fine leaving things for 0.47.1 or 0.48.
participants (4)
-
unknown＠example.com -
Bob Jamison -
Jon A. Cruz -
Tavmjong Bah