From: Guy K. K. <g....@ma...> - 2009-06-21 05:40:33
|
Hi, I've been playing a bit with PovExport as provided in the FAQ. Works quite nicely so far, but ... * There's a bug with drawing arrows. An arrow is a hybrid, POVray wants a transparency, not an opacity. So the transparency() function is applied twice, and arrows are not visible, or their transparency is inverted. * Simple solution: Create a function get_opacity() in the same way as transparency(), but "invert" the behaviour (not "1.0 - a", but "a", and not "1.0" but "0.0" in the else clause) * the povexport module does not handle arrows properlyh that have a changed shaftwidth. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Bruce S. <Bru...@nc...> - 2009-06-21 05:52:21
|
Are you using povexport-2009-06-14? I think the bugs you describe have been fixed in that recently posted version. Also, there was a bug in Visual 5.1 with respect to shaftwidth which affected povexport, and that bug has been fixed with the new Visual 5.11. Bruce Sherwood Guy K. Kloss wrote: > Hi, > > I've been playing a bit with PovExport as provided in the FAQ. Works quite > nicely so far, but ... > > * There's a bug with drawing arrows. An arrow is a hybrid, POVray wants > a transparency, not an opacity. So the transparency() function is applied > twice, and arrows are not visible, or their transparency is inverted. > > * Simple solution: Create a function get_opacity() in the same way as > transparency(), but "invert" the behaviour (not "1.0 - a", but "a", and > not "1.0" but "0.0" in the else clause) > > * the povexport module does not handle arrows properlyh that have a changed > shaftwidth. > > Guy > > |
From: Guy K. K. <g....@ma...> - 2009-06-21 06:16:34
|
On Sun, 21 Jun 2009 17:51:55 Bruce Sherwood wrote: > Are you using povexport-2009-06-14? I think the bugs you describe have > been fixed in that recently posted version. I'm using the one which is linked in the FAQ, and that is povexport-2008-11-25.zip > Also, there was a bug in Visual 5.1 with respect to shaftwidth which > affected povexport, and that bug has been fixed with the new Visual 5.11. No, still on 5.0. Don't want to bother going towards > 5.0, unless I see some necessity in it for me right now, as I'm quite busy with my thesis ... But will, if I see a reasonable benefit for me. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Bruce S. <Bru...@nc...> - 2009-06-21 19:28:48
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Thanks for the info. That FAQ link is now fixed.<br> <br> I believe that if you use the latest povexport you'll find that the arrow opacity issue has been fixed (thanks to Scott David Daniels).<br> <br> The arrow shaftwidth bug isn't a povexport bug but rather a bug in Visual 5.1, corrected in Visual 5.11. However, if you don't wish to upgrade to 5.11 right away, there's a workaround: In your VPython program, explicitly set headwidth=2*shaftwidth and headlength=3*shaftwidth. You'll find that in your existing program (pre-5.11) if after changing shaftwidth you print headwidth and headlength you see the wrong values, though the correct values are used in the display of the arrow. What Visual 5.11 does is report the values of headwidth and headlength that are actually used in displays.<br> <br> Bruce Sherwood<br> <br> Guy K. Kloss wrote: <blockquote cite="mid:200...@ma..." type="cite"> <pre wrap="">On Sun, 21 Jun 2009 17:51:55 Bruce Sherwood wrote: </pre> <blockquote type="cite"> <pre wrap="">Are you using povexport-2009-06-14? I think the bugs you describe have been fixed in that recently posted version. </pre> </blockquote> <pre wrap=""><!----> I'm using the one which is linked in the FAQ, and that is povexport-2008-11-25.zip </pre> <blockquote type="cite"> <pre wrap="">Also, there was a bug in Visual 5.1 with respect to shaftwidth which affected povexport, and that bug has been fixed with the new Visual 5.11. </pre> </blockquote> <pre wrap=""><!----> No, still on 5.0. Don't want to bother going towards > 5.0, unless I see some necessity in it for me right now, as I'm quite busy with my thesis ... But will, if I see a reasonable benefit for me. Guy </pre> </blockquote> </body> </html> |
From: Guy K. K. <g....@ma...> - 2009-06-21 23:05:39
|
On Mon, 22 Jun 2009 07:28:47 you wrote: > Thanks for the info. That FAQ link is now fixed. That's odd, I still see a link to povexport-2008-11-25.zip here: * http://vpython.wikidot.com/ * http://www.vpython.org/FAQ.html But none to a newer version. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Bruce S. <Bru...@nc...> - 2009-06-21 23:16:04
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Sigh. Thanks. Now fixed in those two places, too.<br> <br> The standard place where I had made the fix is in the Documentation section of vpython.org, reached by clicking on "Documentation" on the home page of vpython.org.<br> <br> Note that <a class="moz-txt-link-freetext" href="http://www.vpython.org/FAQ.html">http://www.vpython.org/FAQ.html</a> is in the "old" Visual 3 section of vpython.org, which will eventually go away after a decent interval.<br> <br> Bruce Sherwood<br> <br> Guy K. Kloss wrote: <blockquote cite="mid:200...@ma..." type="cite"> <pre wrap="">On Mon, 22 Jun 2009 07:28:47 you wrote: </pre> <blockquote type="cite"> <pre wrap="">Thanks for the info. That FAQ link is now fixed. </pre> </blockquote> <pre wrap=""><!----> That's odd, I still see a link to povexport-2008-11-25.zip here: * <a class="moz-txt-link-freetext" href="http://vpython.wikidot.com/">http://vpython.wikidot.com/</a> * <a class="moz-txt-link-freetext" href="http://www.vpython.org/FAQ.html">http://www.vpython.org/FAQ.html</a> But none to a newer version. Guy </pre> </blockquote> </body> </html> |
From: Guy K. K. <g....@ma...> - 2009-06-22 04:30:40
Attachments:
povexport.py.diff
|
Hi Bruce, On Mon, 22 Jun 2009 07:28:47 Bruce Sherwood wrote: > I believe that if you use the latest povexport you'll find that the arrow > opacity issue has been fixed (thanks to Scott David Daniels). I've just given it a shot, and it didn't really do the trick for me, either. There are still two bugs in the module: * The box for the arrow does not take the (calculated) value sw in the function, but uses a.shaftwidth directly * For very long arrows the box becomes too thin. To mock the behaviour as in VPython the shaftwidth should be limited to 1/50 th of the arrow length. Attached is a minimal patch against the 2009-06-14 version that should fix that. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Guy K. K. <g....@ma...> - 2009-06-22 05:28:58
Attachments:
povexport_text.py.diff
|
Attached a patch for a first attempt to also do labels. Unfortunately I know by far too little about POVray, so it's quite a feeble attempt on that. But it *does* produce some text output at the right places, in the right text colour, just not rotated and sized properly. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Guy K. K. <g....@ma...> - 2009-06-22 05:33:57
|
On Mon, 22 Jun 2009 17:29:06 Guy K. Kloss wrote: > Unfortunately I know by far too little about POVray, so it's quite a feeble > attempt on that. But it *does* produce some text output at the right > places, in the right text colour, just not rotated and sized properly. Maybe this gives some insight for someone with more POVray experience: http://news.povray.org/povray.text.tutorials/message/<b27i0tg8l509mufq63lg56efmdotq6kgqs%404ax.com>/#<b27i0tg8l509mufq63lg56efmdotq6kgqs%404ax.com> Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Bruce S. <Bru...@nc...> - 2009-06-23 17:14:11
|
Thanks much for these improvements! I'll get these into the posted version. Bruce Sherwood Guy K. Kloss wrote: > Attached a patch for a first attempt to also do labels. > > Unfortunately I know by far too little about POVray, so it's quite a feeble > attempt on that. But it *does* produce some text output at the right places, > in the right text colour, just not rotated and sized properly. > > Guy > > > |