On 2013-01-29 20:54-0800 Alan W. Irwin wrote: > N.B. I know there are some integer ==> PLFLT pen width changes that > should be done in various bindings such as the ones I mentioned to > Jerry above. But currently most of these appear to be covered up by > implicit casting. We need some systematic testing that e.g., -width > 0.3 works for -dev xcairo for _non-C_ examples to find these instances > and fix them. However, I won't have time for that so I will leave > chasing those down to someone else. > > I do plan to still take responsibility for getting -width values less > than 1. to give good results for the qt devices just like they now do > for the cairo devices, and I also need to implement a plwid in > pldeprecated.c for backward compatibility but that is about all I have > time for.
I have accomplished those two final goals of my floting-point pen width plan as of revision 12290. During testing of this revision I discovered one other qt issue which is that -width always applied a uniform pen width of 1.0 regardless of the value specified for width. e.g., -width 100. gave the same results -width 1.0 for qt devices. cairo devices did not have this issue. Because of this issue, to test the above qt changes by temporarily making a call to plwidth(0.2) from examples/c/x01c.c, and that gave very thin lines for all qt devices. That is, that way of applying a pen width change works fine for qt, but not via the -width command-line option for some reason. The status is floating point pen widths now fundamentally work well for our two best device drivers (qt and cairo). However, there are some known leftover issues that need to be polished up such as the qt issue with -width above, the Ada and OCaml issues I pointed out before, and the pllegend and plshade(s) API issues for pen width arguments we discussed previously. Also, this has been a quite intrusive change so undoubtedly there are some unknown issues that have been introduced as well by this change despite my good success with running the test_noninteractive and test_interactive targets. I am going to leave it to others here to polish up the rest of these issues because of constraints on how much time I can spend on PLplot. But I am very pleased that thin line widths < 1.0 work well now for both the cairo and qt devices drivers (our two best device drivers), and there are no obvious run-time issues that show up during all the tests associated with the test_noninteractive and test_interactive targets. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
