From: <hba...@us...> - 2011-10-13 00:35:16
|
Revision: 11951 http://plplot.svn.sourceforge.net/plplot/?rev=11951&view=rev Author: hbabcock Date: 2011-10-13 00:35:06 +0000 (Thu, 13 Oct 2011) Log Message: ----------- Update ChangeLog.release for the 5.9.9 release. Modified Paths: -------------- trunk/ChangeLog.release Modified: trunk/ChangeLog.release =================================================================== --- trunk/ChangeLog.release 2011-10-11 04:07:48 UTC (rev 11950) +++ trunk/ChangeLog.release 2011-10-13 00:35:06 UTC (rev 11951) @@ -1,7927 +1,723 @@ ------------------------------------------------------------------------ -r11830 | hbabcock | 2011-08-01 08:54:13 -0400 (Mon, 01 Aug 2011) | 1 line +r11950 | airwin | 2011-10-11 00:07:48 -0400 (Tue, 11 Oct 2011) | 2 lines Changed paths: - M /trunk/cmake/modules/plplot_version.cmake + M /trunk/README.release -Update date and version number for the 5.9.8 release. Increment SOVERSION for the libplplotd and libplplotcxxd libraries to reflect backwards incompatible API changes made in this version. ------------------------------------------------------------------------- -r11829 | airwin | 2011-07-31 04:58:36 -0400 (Sun, 31 Jul 2011) | 14 lines -Changed paths: - M /trunk/scripts/comprehensive_test.sh +Update my valgrind test results. -Implement do_clean_as_you_go option to clean up as you go. However, it -does not work well, yet, because the custom commands OUTPUT files -just refer to the files from the first example rather than all 33 so -those first example files are the only ones cleaned (so far). - -ToDo (some time in next release cycle) implement complete OUTPUT files -for custom commands. - -Change launch of ctest job to execution of ctest. This probably takes -longer (at least until we make ctest parallel), but it does allow -clean up afterwards since this change makes ctest end become -completely predictable within the scripts. - - ------------------------------------------------------------------------ -r11828 | airwin | 2011-07-31 03:30:27 -0400 (Sun, 31 Jul 2011) | 3 lines +r11949 | airwin | 2011-10-11 00:07:01 -0400 (Tue, 11 Oct 2011) | 3 lines Changed paths: - M /trunk/examples/java/Makefile.examples.in - M /trunk/examples/ocaml/Makefile.examples.in + M /trunk/lib/qsastime/qsastime.c -Add example 33 to those which are built for the traditional install -tree. +Correctly initialize the index used for the bhunt_search. +This fix corrects undefined valgrind warnings for example 29. ------------------------------------------------------------------------ -r11827 | airwin | 2011-07-31 02:49:51 -0400 (Sun, 31 Jul 2011) | 3 lines +r11947 | hezekiahcarty | 2011-10-10 10:36:09 -0400 (Mon, 10 Oct 2011) | 1 line Changed paths: - M /trunk/examples/d/Makefile.examples.in + M /trunk/README.release -Include 33rd example in list of those that are built in the traditional -install tree approach. - +Update README.release with further testing results ------------------------------------------------------------------------ -r11826 | airwin | 2011-07-29 15:50:14 -0400 (Fri, 29 Jul 2011) | 4 lines +r11946 | hezekiahcarty | 2011-10-10 09:38:01 -0400 (Mon, 10 Oct 2011) | 1 line Changed paths: - M /trunk/ABOUT + M /trunk/README.release -More tweaking including spelling issues found by ispell, some grammar -tweaking on the questions, and mentioning -http://www.ohloh.net/p/plplot/contributors. - +Update README.release with more information on the OCaml bindings ------------------------------------------------------------------------ -r11825 | hbabcock | 2011-07-29 13:34:46 -0400 (Fri, 29 Jul 2011) | 1 line +r11945 | hezekiahcarty | 2011-10-10 09:37:55 -0400 (Mon, 10 Oct 2011) | 1 line Changed paths: - M /trunk/ABOUT + M /trunk/cmake/modules/ocaml.cmake -Add a description of the PLplot roadmap (or lack thereof). Tweak the formatting a bit. +Re-enable the OCaml bindings by default ------------------------------------------------------------------------ -r11824 | airwin | 2011-07-27 00:26:10 -0400 (Wed, 27 Jul 2011) | 2 lines +r11944 | airwin | 2011-10-10 01:47:24 -0400 (Mon, 10 Oct 2011) | 2 lines Changed paths: - M /trunk/ABOUT + M /trunk/README.release -Set appropriate properties for this file. +Update status of OCaml testing. ------------------------------------------------------------------------ -r11823 | airwin | 2011-07-27 00:06:47 -0400 (Wed, 27 Jul 2011) | 3 lines +r11943 | airwin | 2011-10-09 17:53:58 -0400 (Sun, 09 Oct 2011) | 10 lines Changed paths: - M /trunk/ABOUT + M /trunk/README.release -Add an extensive section on usage statistics, a minor section -on our developers, and many tweaks. +Reorganize in preparation for the forthcoming 5.9.9 release including removal +of all the remarks about changes relative to the 5.9.7 release, official +notices concerning the broken build fixes for Windows, and the disabling +of ocaml by default. Also add detailed listing of all the testing done +for this release. ------------------------------------------------------------------------- -r11822 | hbabcock | 2011-07-26 20:30:08 -0400 (Tue, 26 Jul 2011) | 1 line -Changed paths: - A /trunk/ABOUT +Spell check. -Initial version of a ABOUT file that provides a brief overview of the PLplot project. ------------------------------------------------------------------------- -r11821 | smekal | 2011-07-19 11:46:38 -0400 (Tue, 19 Jul 2011) | 1 line -Changed paths: - M /trunk/drivers/wxwidgets_gc.cpp -The text clipping didn't work for wxWidgets 2.9.2/Cocoa/Mac since the wxRegion constructor used wasn't implemented. Only for this wxWidgets configuration another wxRegion constructor is used. Apart from that there was no problem using the new wxWidgets version (which soon will become 3.0.0) with the PLplot wxWidgets driver. ------------------------------------------------------------------------- -r11820 | airwin | 2011-07-18 01:34:57 -0400 (Mon, 18 Jul 2011) | 18 lines -Changed paths: - M /trunk/src/pllegend.c -Improve internal documentation of calculate_limits so that it -is more obvious what is being calculated. - -Distinguish arguments for calls to calculate_limits more carefully -to keep track of everything necessary for calculating offsets -and sizes of bounding boxes for undecorated colorbar, decorated -colorbar, and labelled and decorated colorbar. - -Implement bounding box calculation in draw_label so that the overall -bounding box (for labelled and decorated colorbar) will (finally) be -correct. This change has been tested for long labels for plcolorbar -in example 33 where both x and y bounding box limits are increased as -well as the standard short labels for plcolorbar in example 33. - -This commit completes my planned work on the bounding box and -position calculations for plcolorbar. - - ------------------------------------------------------------------------ -r11819 | smekal | 2011-07-17 15:38:33 -0400 (Sun, 17 Jul 2011) | 1 line +r11942 | airwin | 2011-10-09 15:58:44 -0400 (Sun, 09 Oct 2011) | 5 lines Changed paths: - M /trunk/drivers/wxwidgets_gc.cpp + M /trunk/cmake/modules/ocaml.cmake -Fixed a memory allocation bug, which showed up if one resizes the window. ------------------------------------------------------------------------- -r11818 | airwin | 2011-07-17 13:34:03 -0400 (Sun, 17 Jul 2011) | 12 lines -Changed paths: - M /trunk/src/pllegend.c +Disable OCaml by default for this forthcoming release because of the +segfault issue and other mememory management issues that I have +spotted with valgrind. -Make second call to calculate_limits with appropriate transformation -of input and output results. Since additional coordinate system -tranformations are involved the results are numerically different, but -the ndiff app confirms these changes are only for -one unit in the last PostScript place. That numerical result helps -to verify that the correct transformations are being used for -the second calculate_limits call. -ToDo: Implement bounding box calculation in draw_label so that the -overall position and bounding box will (finally) be correct. - - ------------------------------------------------------------------------ -r11817 | airwin | 2011-07-17 12:30:21 -0400 (Sun, 17 Jul 2011) | 29 lines +r11941 | airwin | 2011-10-08 19:31:57 -0400 (Sat, 08 Oct 2011) | 6 lines Changed paths: - M /trunk/src/pllegend.c + M /trunk/cmake/modules/ocaml.cmake -Code reorganization in preparation for calculating complete bounding box -and position of the labelled and decorated colorbar. +Disable OCaml by default for static build until rpath issues are +straightened out. Note, there is now a new option available called +ENABLE_ocaml_static which defaults to OFF, but if you set it to ON +you will get a build of OCaml for that static case. -Systematically use the mm form of bounding box limits, -plsc->boxbb_xmin, etc., rather than the confusing mixture of that form -and one where the limits are expressed in normalized subpage -coordinates. -Implement the static function, calculate_limits, to isolate in one -place all the limit changes due to a changed bounding box. The first -call of this function is associated with changing the bounding box and -corresponding position calculation from the undecorated colorbar to -the decorated (ticks, numerical tick labels, and exponents) colorbar. -The second call of this function (not yet used) will be associated -with changing the bounding box and corresponding position -calculationfrom the decorated colorbar to the labelled and decorated -colorbar. - -However, the calculate_limits code is not yet fully -understood/documented (since it just collected pre-existing code which -was not fully understood/documented into a static function) so the -second call is not used yet. - -As expected, the result is identical to the previous commit, i.e., -labels are currently ignored in the bounding box calculation and in -the calculation of the position of that bounding box in the overall -plot. - - ------------------------------------------------------------------------ -r11816 | airwin | 2011-07-14 12:37:58 -0400 (Thu, 14 Jul 2011) | 3 lines +r11940 | arjenmarkus | 2011-10-07 03:20:10 -0400 (Fri, 07 Oct 2011) | 3 lines Changed paths: - M /trunk/examples/c/x33c.c + M /trunk/bindings/f77/plplotf77_ifort.def + M /trunk/bindings/f77/plplotf77_mingw.def + M /trunk/bindings/f77/plstubs.h -Decrease size of overall viewport so there is room to display labelled -and decorated colorbar. +Correct a typo in the export definitions for Intel Fortran. Add a missing entry (plsettransform). +With these changes PLplot is built smoothly for the combination MSVC/C++ (9.0) and Intel Fortran (11.1) ------------------------------------------------------------------------ -r11815 | airwin | 2011-07-14 12:36:01 -0400 (Thu, 14 Jul 2011) | 10 lines +r11939 | arjenmarkus | 2011-10-07 03:00:30 -0400 (Fri, 07 Oct 2011) | 1 line Changed paths: M /trunk/src/pllegend.c -Draw overall label relative to the bounding box of the rest of the -decorated (including tick marks, numerical labels for ticks, -exponents, and end caps) colorbar. This change greatly simplifies -the draw_box arguments and logic, and makes a much nicer-looking -result. - -ToDo: Calculate complete bounding box of label + rest of the decorated -colorbar. - - +Change max_opts into a preprocessor macro, because MS Visual C/C++ does not like "automatic" arrays. ------------------------------------------------------------------------ -r11814 | airwin | 2011-07-13 18:49:07 -0400 (Wed, 13 Jul 2011) | 8 lines +r11938 | airwin | 2011-10-06 14:13:58 -0400 (Thu, 06 Oct 2011) | 22 lines Changed paths: - M /trunk/src/pllegend.c + M /trunk/include/ltdl_win32.h + M /trunk/src/ltdl_win32.c -Reorganize plcolorbar code so the overall colorbar label is drawn with -the separate static function draw_label. This reorganization gives -identical example 33 results to before and prepares the way to -reposition the label to be centred relative to the bounding box of the -inner decorated box and to also do bounding box calculations for the -whole object (label + inner bounding box). +Fix for Windows broken build for the 5.9.8 release. This fix supplies +a needed lt_dlmakeresident routine for ltdl_win32.c so that dynamic +devices can be built on Windows. Currently, this version of +lt_dlmakeresident does nothing but return success. The net result is +that on Windows plend will unload all libraries that our dynamic +devices depend on just like what happened for 5.9.7. +Note that for Linux we found that if we did not call the +lt_dlmakeresident version for libltdl, that calls to plend (which in +turn call lt_dlexit()) unloaded the external libraries that are +depended on by our dynamic devices. That library unloading sometimes +lead to exit handler errors for those libraries on Linux. ------------------------------------------------------------------------- -r11813 | airwin | 2011-07-13 18:02:56 -0400 (Wed, 13 Jul 2011) | 17 lines -Changed paths: - M /trunk/src/pllegend.c +In the future if library unloading also leads to issues for Windows, +we will need to add real functionality to the lt_dlmakeresident +function in ltdl_win32.c to also avoid unloading the libraries in that +case. However, we have no reports of such library unloading +issues on Windows so a lt_dlmakeresident version for ltdl_win32.h that +does nothing other than return success is all we appear to need at +the present time. -Fix accident waiting to happen for get_subpage_per_mm (a static -function which is called directly or indirectly by pllegend and plcolorbar). -The only reason this function worked correctly before was it was always -called after - -plvpor( 0., 1., 0., 1. ); -plwind( 0., 1., 0., 1. ); - -But the point is the get_subpage_per_mm doesn't need to know anything -about the viewport, and a call to plgspa returns all data required to -calculate the x and y ratios of normalized subpage coordinates to mm. -So get_subpage_per_mm can be substantially simplified, and that -simplification insures that routine will give correct results when -plvpor and plwind have been called with other than the above values. - - ------------------------------------------------------------------------ -r11812 | airwin | 2011-07-12 17:52:45 -0400 (Tue, 12 Jul 2011) | 8 lines +r11936 | airwin | 2011-09-25 12:40:30 -0400 (Sun, 25 Sep 2011) | 5 lines Changed paths: - M /trunk/src/pllegend.c - -Fix memory management issues with draw_box (static function called by -plcolorbar). - -Implement draw_box documentation. - -Improve plcolorbar documentation and parameter sanity checking/defaults. - - ------------------------------------------------------------------------- -r11811 | airwin | 2011-07-12 01:48:39 -0400 (Tue, 12 Jul 2011) | 10 lines -Changed paths: - M /trunk/src/plbox.c - -Implement bounding-box functionality for horizontal and vertical axes -of custom labels following what is done in plbox. The bounding-box -results for custom labels look the same (good) as for more ordinary -labels done with plbox in example 33. - -ToDo: For plcolorbar still need to implement adjustment of overall -colorbar label position relative to plbox bounding box and implement -bounding-box functionality for (moved) overall colorbar label. - - ------------------------------------------------------------------------- -r11810 | airwin | 2011-07-12 00:16:54 -0400 (Tue, 12 Jul 2011) | 9 lines -Changed paths: - M /trunk/src/plbox.c - -Update bounding box to include vertical axis exponents for plbox -bounding box. Example 33 confirms this improvement is working -properly. This completes the bounding box calculation for plbox! - -ToDo: For plcolorbar still need to implement bounding-box -functionality for horizontal and vertical axes of custom labels and -bounding-box functionality for overall colorbar label. - - ------------------------------------------------------------------------- -r11809 | airwin | 2011-07-11 21:47:09 -0400 (Mon, 11 Jul 2011) | 7 lines -Changed paths: - M /trunk/src/pllegend.c - -For some reason, plgradient gives unreliable results when the x and y -world coordinates have vastly different magnitudes. Work around this -issue, by changing the world coordinates of the direction perpendicular -to the plcolorbar from {0., 1.} to {0., max_abs} where max_abs is -the maximum of the absolute values of the minimum and maximum of -the world coordinate range being plotted by the colorbar. - ------------------------------------------------------------------------- -r11808 | airwin | 2011-07-11 18:11:54 -0400 (Mon, 11 Jul 2011) | 13 lines -Changed paths: - M /trunk/src/plbox.c - -Update bounding box to include both vertical and horizontal components -of numerical labelling of vertical axes. Example 33 confirms this -improvement is working properly. This completes (aside from the -vertical axis exponents) the bounding box calculation for vertical -axes of plbox which has been verified using example 33 with and without -the "v" option in axis_opts. - -ToDo: Still need to implement vertical axis exponents for plbox -bounding box. For plcolorbar also need to implement bounding-box -functionality for horizontal and vertical axes of custom labels and -bounding-box functionality for overall colorbar label. - - ------------------------------------------------------------------------- -r11807 | airwin | 2011-07-11 18:04:24 -0400 (Mon, 11 Jul 2011) | 2 lines -Changed paths: - M /trunk/src/pllegend.c - -Fix small error in line-style restoration. - ------------------------------------------------------------------------- -r11806 | airwin | 2011-07-11 18:03:15 -0400 (Mon, 11 Jul 2011) | 3 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Use negative numbers in range to make sure bounding-box calculation is -still good for that. (It was.) - ------------------------------------------------------------------------- -r11805 | airwin | 2011-07-11 17:33:12 -0400 (Mon, 11 Jul 2011) | 3 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Show how to test parallel axis labels for vertical axis of colorbars, -but comment out (now that I have finished that test). - ------------------------------------------------------------------------- -r11804 | airwin | 2011-07-10 13:27:00 -0400 (Sun, 10 Jul 2011) | 18 lines -Changed paths: - M /trunk/drivers/pdf.c - -Use plP_script_scale method to replace idiosyncratic method of -determining superscript/subscript font sizes and offsets. The -test_superscript_subscript.py results are much improved by this -change. - -However, a vertical offset issue for the pdf device driver that was -evident before this change still continues; superscript offsets shift -the entire string downwards (including all text before when "#u" is -used) while the corresponding result for subscripts (when "#d" is -used) has no such effect. I have looked hard for the origin of this -pdf bug but cannot find the source of it. The superscript and -subscript paths are absolutely identical in the code except for the -numerical calculation of dev->yOffset. So why does the correct offset -from the baseline being calculated in both cases affect the overall -baseline (including the unsuperscripted/unsubscripted _prior_ parts of -the string) in the superscript case but not in the subscript case? - - ------------------------------------------------------------------------- -r11803 | airwin | 2011-07-10 13:08:00 -0400 (Sun, 10 Jul 2011) | 6 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Use more regular vertical alignment of strings. - -Add some fiducial marks for the second page that clearly demonstrate vertical -offset problems with the pdf device driver. - - ------------------------------------------------------------------------- -r11802 | airwin | 2011-07-09 19:11:55 -0400 (Sat, 09 Jul 2011) | 2 lines -Changed paths: - M /trunk/doc/docbook/src/api.xml - -State that plspage and plgpage are also used in example 14. - ------------------------------------------------------------------------- -r11801 | airwin | 2011-07-08 21:51:34 -0400 (Fri, 08 Jul 2011) | 2 lines -Changed paths: - M /trunk/drivers/svg.c - -Oops. Style previous commit. - ------------------------------------------------------------------------- -r11800 | airwin | 2011-07-08 21:49:33 -0400 (Fri, 08 Jul 2011) | 6 lines -Changed paths: - M /trunk/drivers/svg.c - -Use plP_script_scale method to replace idiosyncratic method of -determining superscript/subscript font sizes and offsets. The -test_superscript_subscript.py results are much improved by this -change. - - ------------------------------------------------------------------------- -r11799 | airwin | 2011-07-07 16:56:29 -0400 (Thu, 07 Jul 2011) | 9 lines -Changed paths: - M /trunk/drivers/cairo.c - -Use plP_script_scale to calculate superscript/subscript font scale -factors and vertical offsets. The results are identical with the -previous version of this code that made these calculations -independently of plP_script_scale. Note plP_script_scale arguments -must be stored externally, and for the alt_unicode approach this -storage is necessarily in aStream to preserve the values of these -arguments between plP_script_scale calls. - - ------------------------------------------------------------------------- -r11798 | hbabcock | 2011-07-06 13:28:53 -0400 (Wed, 06 Jul 2011) | 1 line -Changed paths: - M /trunk/drivers/cairo.c - -Fix offset bug in the standard unicode pathway. The problem was that aStream->fontSize is only set in the alt-unicode pathway so the local variable fontSize should be used instead for calculating the text Y offset. ------------------------------------------------------------------------- -r11797 | airwin | 2011-07-06 01:48:58 -0400 (Wed, 06 Jul 2011) | 6 lines -Changed paths: - M /trunk/drivers/ps.c - -Use plP_script_scale method to replace idiosyncratic method of -determining superscript/subscript font sizes and offsets. The -test_superscript_subscript.py results are much improved by this -change. - - ------------------------------------------------------------------------- -r11796 | airwin | 2011-07-06 00:50:37 -0400 (Wed, 06 Jul 2011) | 5 lines -Changed paths: - M /trunk/bindings/qt_gui/plqt.cpp - -Bug fix. Restore currentFontScale default value that was -inadvertently removed by the last commit. This bug affected text for -a number of qt devices. - - ------------------------------------------------------------------------- -r11795 | airwin | 2011-07-05 22:28:50 -0400 (Tue, 05 Jul 2011) | 8 lines -Changed paths: - M /trunk/drivers/psttf.cc - M /trunk/scripts/style_source.sh - -Include drivers/psttf.cc in list of C++ source files to style. (This -file was inadvertently left out from the original list of source files -to style.) - -Many changes were introduced by the styling of psttfc.cc, but the -results are the same as for the previous unstyled file. - - ------------------------------------------------------------------------- -r11794 | airwin | 2011-07-05 22:23:16 -0400 (Tue, 05 Jul 2011) | 2 lines -Changed paths: M /trunk/src/plcore.c -Style previous commit. +Allow plend to completely remove certain of our device drivers that do +not depend on any libraries other than libplplotd. This change restores clean +valgrind results for, e.g., -dev svg and -dev psc. ------------------------------------------------------------------------- -r11793 | hbabcock | 2011-07-05 22:20:57 -0400 (Tue, 05 Jul 2011) | 1 line -Changed paths: - M /trunk/drivers/cairo.c -Attempt to fix vertical offset problems with strings that contain sub/superscripts. Add string length functionality to the -classic- text rendering path so that it again renders text properly. However the -classic- path is still not completely fixed as there still seems to a offset problem. ------------------------------------------------------------------------ -r11792 | airwin | 2011-07-05 22:14:40 -0400 (Tue, 05 Jul 2011) | 6 lines +r11935 | airwin | 2011-09-25 12:09:38 -0400 (Sun, 25 Sep 2011) | 2 lines Changed paths: - M /trunk/drivers/psttf.cc - -Use plP_script_scale method to replace idiosyncratic method of -determining superscript/subscript font sizes and offsets. The -test_superscript_subscript.py results are much improved by this -change. - - ------------------------------------------------------------------------- -r11791 | airwin | 2011-07-05 15:06:12 -0400 (Tue, 05 Jul 2011) | 5 lines -Changed paths: + M /trunk/bindings/c++/plstream.cc M /trunk/bindings/qt_gui/plqt.cpp - -Replace idiosyncratic method of calculating superscript/subscript -offsets and font sizes with standard (plP_script_scale) method. -The test_superscript_subscript.py results are much improved by this -change. - ------------------------------------------------------------------------- -r11790 | airwin | 2011-07-05 13:36:24 -0400 (Tue, 05 Jul 2011) | 5 lines -Changed paths: - M /trunk/drivers/cairo.c - -Replace generic "smaller" sizes for each superscript/subscript level -by exact calculated font sizes appropriate for that level. - -Some code cleanup and improved commentary. - ------------------------------------------------------------------------- -r11789 | airwin | 2011-07-05 13:18:50 -0400 (Tue, 05 Jul 2011) | 8 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -serif ==> italic to distinguish visual results more clearly when a font -is changed in the middle of a superscript/subscript level. - -Note that -dev qtwidget changes to the italic font at the correct -point in the string. -dev xcairo changes to the italic font for the -_entire_ string (which demonstrates a current cairo bug). - - ------------------------------------------------------------------------- -r11788 | hbabcock | 2011-07-05 13:03:51 -0400 (Tue, 05 Jul 2011) | 1 line -Changed paths: - M /trunk/src/plcore.c - -Fix yet another bug in the alternate unicode pathway which was the source of strange font choices in strings that contained more than one font. ------------------------------------------------------------------------- -r11787 | airwin | 2011-07-04 16:25:58 -0400 (Mon, 04 Jul 2011) | 5 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Change to a serif font in the middle of non-zero superstring/substring -levels to demonstrate more clearly the font-changing issue with the -cairo devices (the font is changed for the whole string and not -just the part beyond the FCI command). - ------------------------------------------------------------------------- -r11786 | airwin | 2011-07-04 16:22:44 -0400 (Mon, 04 Jul 2011) | 11 lines -Changed paths: - M /trunk/drivers/cairo.c - -Fix obvious bug in order in which superscript/subscript level is -restored for open_span_tag. This fixes the cairo device driver -vertical offset issues for test_superscript_subscript.py where FCI -commands occur at non-zero superscript/subscript levels. - -However, this test case also shows an additional issue still remains for -the cairo devices. If you change font in the middle of a -superscript/subscript, it applies to the whole string, not just -that part of the string beyond where the font change is applied. - - ------------------------------------------------------------------------- -r11785 | airwin | 2011-07-04 15:54:19 -0400 (Mon, 04 Jul 2011) | 2 lines -Changed paths: - M /trunk/include/plplotP.h - M /trunk/src/plsym.c - -Style previous changes. - ------------------------------------------------------------------------- -r11784 | airwin | 2011-07-04 15:37:47 -0400 (Mon, 04 Jul 2011) | 7 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Include an FCI command (to change to bold face) in one superscript and -one subscript test case. This works correctly for qt devices, but -fails to give good results for the cairo devices demonstrating a bug -for those devices for this corner case (FCI and non-zero -superscript/subscript level). - - ------------------------------------------------------------------------- -r11783 | airwin | 2011-07-03 13:06:18 -0400 (Sun, 03 Jul 2011) | 18 lines -Changed paths: - M /trunk/include/plplotP.h - M /trunk/src/plsym.c - -Implement a private plP_script_scale function that calculates scale -values for font size and magnitude of the vertical offset associated -with superscripts/subscripts. Currently, the font scale and offset -calculations associated with superscripts and subscripts are done in -an idiosyncratic (and often incorrect) way in various locations within -the core code and drivers. plP_script_scale is designed to -consolidate those bits of logic in one place where the calculation is -done correctly. - -As a first use of this new logic, use plP_script_scale for the Hershey -font superscripts/subscripts. plP_script_scale produces completely -symmetrical vertical offsets between superscripts and subscripts. -Therefore, this change corrects a very long-standing error (since -before 1993) in the vertical offset of the Hershey subscripts which -previously were not consistent with the magnitude of the vertical -offsets of the superscripts. - - ------------------------------------------------------------------------- -r11782 | airwin | 2011-07-01 02:27:21 -0400 (Fri, 01 Jul 2011) | 3 lines -Changed paths: - M /trunk/examples/python/CMakeLists.txt - A /trunk/examples/python/test_style.py - -Implement test_style.py to show all possible line patterns and area fill -patterns for display using pllegend. - ------------------------------------------------------------------------- -r11781 | airwin | 2011-06-22 16:45:39 -0400 (Wed, 22 Jun 2011) | 20 lines -Changed paths: - M /trunk/drivers/cairo.c - -I have discovered experimentally that contrary to the documentation at -http://developer.gnome.org/pango/unstable/PangoMarkupFormat.html, rise -is in units of 1024th of a point (i.e., a real distance unit) rather -than in units of the (variable) font size. Implement a correction the -accounts properly for the real units of rise. The result is the actual -superscript/subscript vertical offsets that are rendered by cairo -devices now is (correctly) proportional to the font size (as opposed -to being fixed in size before). This correction solves the second -issue noted in the previous commit. - -The cairo and PLplot character coordinate system have vertical zero -points of respectively the baseline of the fonts and the middle of the -vertical dimension of the fonts. This mismatch in coordinate systems -means the superscript/subscript offsets appear asymmetrical for cairo -devices compared to -dev xwin (i.e., issue 1 noted in the previous -commit message). An approximation for this coordinate shift has been -implemented, and the asymmetry appears to be greatly reduced as a -result. - - ------------------------------------------------------------------------- -r11780 | airwin | 2011-06-22 15:40:38 -0400 (Wed, 22 Jun 2011) | 2 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Tweak whitespace. - ------------------------------------------------------------------------- -r11779 | airwin | 2011-06-21 23:33:31 -0400 (Tue, 21 Jun 2011) | 10 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Implement an additional test which superimposes exponent data you -obtain with badly scaled axes for plbox with similar (using an -exponent of -100 rather than -200) exponent data mimicked with direct -calls to plmtex. This test shows complete agreement in exponent -offsets (and good values for those offsets) between the plbox and -direct calls to plmtex for -dev xwin and -dev xcairo. Thus, it does -not verify the bad vertical plbox exponent offsets that you get for -example 33 using -dev xcairo (but not -dev xwin) - - ------------------------------------------------------------------------- -r11778 | airwin | 2011-06-21 20:46:58 -0400 (Tue, 21 Jun 2011) | 25 lines -Changed paths: - M /trunk/drivers/cairo.c - -Better tuning of superscript/subscript offsets to match algorithm used -for plstr code in plsym.c that is used for Hershey fonts (e.g., -dev -xwin). - -However, there are still at least two superscript/subscript bugs for -the cairo devices. - -1. test_superscript_subscript.py results show that the vertical - offsets for superscripts with -dev xcairo largely match those from - -dev xwin. This is expected because it was those offsets I used to - tune the cairo device driver. However, the subscript vertical - offsets are slightly too large in magnitude, i.e., the subscript - is placed too low compared to the corresponding superscript. - Off by 1 error for subscripts? - -2. The plbox axis exponents that occur for badly scaled axis -coordinates are written using plmtex. I mimic those plmtex calls with -test_superscript_subscript.py. As expected, the exponent strings from -plbox and test_superscript_subscript.py with -dev xwin have the same -vertical offsets. However, the -dev xcairo results for the two cases -are quite different with the plbox result having much too large a -vertical offset for the superscript. Starting superscript offset -level is off by 1 for plbox? - - ------------------------------------------------------------------------- -r11777 | airwin | 2011-06-21 20:26:12 -0400 (Tue, 21 Jun 2011) | 7 lines -Changed paths: - M /trunk/examples/python/test_superscript_subscript.py - -Add the equivalent plmtex superscript and subscript tests to the -previous plptex tests. - -Add four specific plmtex tests that mimic the exponents that occur for -badly scaled plbox axes. - - ------------------------------------------------------------------------- -r11776 | airwin | 2011-06-21 14:08:09 -0400 (Tue, 21 Jun 2011) | 10 lines -Changed paths: - M /trunk/examples/c/x33c.c - M /trunk/src/plbox.c - -Update bounding box to include both vertical and horizontal components -of numerical labelling exponents for horizontal axes. Example 33 -confirms this improvement is working properly. This completes the -bounding box calculation for horizontal axes of plbox. - -ToDo: Need to implement similar functionality for vertical axes of -plbox, horizontal and vertical axes of custom labels, and overall -colorbar label. - - ------------------------------------------------------------------------- -r11775 | airwin | 2011-06-21 12:43:35 -0400 (Tue, 21 Jun 2011) | 9 lines -Changed paths: - M /trunk/src/plbox.c - M /trunk/src/pllegend.c - -Implement bounding box that includes both vertical and horizontal -components of numerical labelling for horizontal axes. Example 33 -confirms this improvement is working properly. - -ToDo: Need to implement similar functionality for exponent of -numerical label (where present), custom labels, vertical axes, and -overall colorbar label. - - ------------------------------------------------------------------------- -r11774 | airwin | 2011-06-20 18:09:33 -0400 (Mon, 20 Jun 2011) | 17 lines -Changed paths: - M /trunk/examples/c/x33c.c - M /trunk/include/plstrm.h - M /trunk/src/plbox.c - M /trunk/src/pllegend.c - -Implement infrastructure for bounding-box calculation for plbox, -label_box, and label_box_custom (including decorations such as -inverted tick marks and numerical tick labels). Use this -infrastructure to help calculate the position of the complete colorbar -(including decorations) and its bounding box. For now, the revised -example 33 shows the effects of inverted tick marks on position and -bounding box of the complete colorbar. - -ToDo: for now, I have only implemented and tested the inverted tick -mark case as a proof of concept for the plbox bounding-box -infrastructure. Thus, additional work needs to be done to include the -numerical tick labels in the bounding box for plbox. Also, the -colorbar label (if present) is independent of plbox so must be -included independently into the bounding box calculation for the -complete colorbar. - - ------------------------------------------------------------------------- -r11773 | airwin | 2011-06-20 14:03:03 -0400 (Mon, 20 Jun 2011) | 2 lines -Changed paths: - M /trunk/bindings/qt_gui/plqt.cpp + M /trunk/drivers/ps.c M /trunk/drivers/qt.cpp - -Style previous changes. - ------------------------------------------------------------------------- -r11772 | hbabcock | 2011-06-17 09:59:51 -0400 (Fri, 17 Jun 2011) | 1 line -Changed paths: - M /trunk/bindings/qt_gui/plqt.cpp - M /trunk/drivers/qt.cpp - -Add (lightly tested) string length functionality to the Qt driver. ------------------------------------------------------------------------- -r11771 | airwin | 2011-06-15 13:06:26 -0400 (Wed, 15 Jun 2011) | 11 lines -Changed paths: - M /trunk/src/pllegend.c - -Smaller cap angles imply large caps which are great for debugging cap -position problems, but as far as I know those are all debugged now so -return cap_angle to a larger cap_angle. I have currently chosen that -to be 90 deg, but we may want to make the cap angle a bit smaller than -that if people prefer a slightly larger cap style. Or we may want -to make this style parameter something that the user can set. - -Adjust label_offset inside plcolorbar to account for exact cap extent. -(This was debugged with a small cap angle ==> large cap.) - - ------------------------------------------------------------------------- -r11770 | airwin | 2011-06-15 12:55:17 -0400 (Wed, 15 Jun 2011) | 2 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Adjust positions of colorbars so that text doesn't get clipped. - ------------------------------------------------------------------------- -r11769 | airwin | 2011-06-14 02:17:38 -0400 (Tue, 14 Jun 2011) | 8 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Plot both background and edge of colorbar bounding box to help -diagnose any colorbar bounding box or positioning issues. For -example, this plot currently demonstrates there are no such issues -associated with the caps, but there continues to be the well-known -issues where the numerical labeling of tick marks and the labels are -currently ignored for bounding box size and position. - - ------------------------------------------------------------------------- -r11768 | airwin | 2011-06-14 02:13:31 -0400 (Tue, 14 Jun 2011) | 10 lines -Changed paths: - M /trunk/src/pllegend.c - -Background part of bounding box is plotted first (while edge line of -bounding box continues to be plotted last). - -Incorporate caps into bounding box. - -Temporarily reduce cap angle to accentuate cap to demonstrate there -are no positioning issues (e.g., bounding boxes are properly centered -for example 33) or bounding-box issues associated with the caps. - - ------------------------------------------------------------------------- -r11767 | airwin | 2011-06-13 12:16:57 -0400 (Mon, 13 Jun 2011) | 10 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/src/pllegend.c - -Adjust viewport and windows coordinate limits consistently so that -image, gradient, and shades colorbars now all have good positioning and -clip results according to the new positioning scheme. - -ToDo: Make bounding box correspond to extent of text outside the core -colorbar and modify colorbar part of example 33 to (a) pack more -results per page, and (b) demonstrate the new colorbar functionality -that has been recently introduced. - - ------------------------------------------------------------------------- -r11766 | airwin | 2011-06-12 19:51:06 -0400 (Sun, 12 Jun 2011) | 12 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/src/pllegend.c - -Update colorbar, tickmarks and numerical labels, and text to use the -new positioning scheme for plcolorbar. - -ToDo: there is still work required to understand and fix the -positioning of the shades case of colorbar and to expand the bounding -box to account for more than just the core colorbar. - -However, if you ignore the shades case (i.e., focus on just the image -and gradient cases) for example 33, the results look reasonable again -so I am getting there. - - ------------------------------------------------------------------------- -r11765 | airwin | 2011-06-12 14:25:19 -0400 (Sun, 12 Jun 2011) | 2 lines -Changed paths: - M /trunk/doc/docbook/src/api.xml - -Tweak documentation of plimage arguments xmin, xmax, ymin, and ymax. - ------------------------------------------------------------------------- -r11764 | airwin | 2011-06-12 14:03:08 -0400 (Sun, 12 Jun 2011) | 23 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/src/pllegend.c - -Fix minor bug in pllegend routine where line style changes could be -propagated outside the routine. - -Drop old version of plcolorbar code since the examples have long since -been inconsistent with that version. - -Improve specification of cap proportions using cap_angle, the angle in -degrees of the angle of the cap triangle that points in the direction -of the orientation of the cap. - -Correctly position boundary box and caps according to the new -positioning scheme. This last is an interim commit to preserve my -current work, and there are a lot more changes to come to correctly -position bar, tickmarks and numerical labels for that bar, and the -descriptive text. Also, the boundary box currently just refers to the -inner bar without extensions (yet) due to caps, numerical labels, and -the descriptive text. - -The result builds without issues, and examples 16 and 33 -run with with no run-time errors for the case where -the -colorbar option is used. - - ------------------------------------------------------------------------- -r11763 | airwin | 2011-06-09 12:31:34 -0400 (Thu, 09 Jun 2011) | 20 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/include/plplot.h - M /trunk/src/pllegend.c - -API change for plcolorbar that adds functionality that is already -available in pllegend. New arguments to return bounding box size -of colorbar, specify a background color for the area contained by the -bounding box (if the PL_COLORBAR_BACKGROUND bit is set in opt), and -specify the line color and line style of a boundary line for the -bounding box (if the PL_COLORBAR_BOUNDING_BOX bit is set in opt). - -Add internal infrastructure to support complete position functionality -that is the same (except for defaults) as already implemented in -pllegend. - -ToDo: the new position functionality is a work in progress with some -remaining coordinate transformation issues so, for example, the size -of the bounding box is currently only correct in the simplest cases, -the bounding box is not yet plotted in the correct place, and the caps -are also not yet plotted in the correct place with the correct size. -But the 16th and 33rd examples do build without errors and run (using -the -colorbar option) without showstopper errors such as segfaults. - - ------------------------------------------------------------------------- -r11762 | airwin | 2011-06-01 20:02:22 -0400 (Wed, 01 Jun 2011) | 2 lines -Changed paths: - M /trunk/src/plctrl.c - -Style previous commit. - ------------------------------------------------------------------------- -r11761 | airwin | 2011-06-01 16:50:58 -0400 (Wed, 01 Jun 2011) | 9 lines -Changed paths: - M /trunk/data/cmap0_alternate.pal - M /trunk/data/cmap0_black_on_white.pal - M /trunk/data/cmap0_default.pal - M /trunk/data/cmap0_white_bg.pal - M /trunk/data/cmap1_blue_red.pal - M /trunk/data/cmap1_blue_yellow.pal - M /trunk/data/cmap1_default.pal - M /trunk/data/cmap1_gray.pal - M /trunk/data/cmap1_highfreq.pal - M /trunk/data/cmap1_lowfreq.pal - M /trunk/data/cmap1_radar.pal - -Set line endings to native for all *.pal files. This change should -leave line endings as LF (Unix) on Unix systems and change them to -(CRLF) on Windows systems for files that are checked out using svn. -This should test Arjen's recent change designed to make the *.pal file -reading programmes work regardless of whether Linux or Windows line -endings are used. The checked out *.pal files definitely work on -Linux, but need testing on Windows. - - ------------------------------------------------------------------------- -r11760 | airwin | 2011-06-01 15:29:11 -0400 (Wed, 01 Jun 2011) | 19 lines -Changed paths: - M /trunk/bindings/c++/plstream.h - M /trunk/bindings/gnome2/lib/gcw-lib.c - M /trunk/bindings/gnome2/lib/plplotcanvas.c - M /trunk/bindings/java/plplotjavac.i - M /trunk/bindings/lua/plplotluac.i - M /trunk/bindings/ocaml/plplot_impl.c - M /trunk/bindings/octave/plplot_octave.i - M /trunk/bindings/python/plplotcmodule.i - M /trunk/bindings/qt_gui/plqt.cpp - M /trunk/bindings/tcl/tclAPI.c - M /trunk/bindings/tcl/tclMatrix.c - M /trunk/bindings/tk/Pltk_Init.c - M /trunk/bindings/tk/plframe.c - M /trunk/bindings/tk/plserver.c - M /trunk/bindings/tk/tkshell.c - M /trunk/bindings/tk-x-plat/Plplotter_Init.c - M /trunk/bindings/tk-x-plat/plplotter.c - M /trunk/bindings/wxwidgets/wxPLplotstream.cpp - M /trunk/bindings/wxwidgets/wxPLplotwindow.cpp - M /trunk/bindings/wxwidgets/wxPLplotwindow.h - M /trunk/drivers/aqt.c - M /trunk/drivers/cairo.c - M /trunk/drivers/gcw.c - M /trunk/drivers/pbm.c - M /trunk/drivers/pdf.c - M /trunk/drivers/qt.cpp - M /trunk/drivers/svg.c - M /trunk/drivers/tk.c - M /trunk/drivers/tkwin.c - M /trunk/drivers/wingcc.c - M /trunk/drivers/wxwidgets.cpp - M /trunk/drivers/wxwidgets_agg.cpp - M /trunk/drivers/wxwidgets_app.cpp - M /trunk/drivers/wxwidgets_dc.cpp M /trunk/drivers/wxwidgets_gc.cpp - M /trunk/examples/c++/x08.cc - M /trunk/examples/c++/x09.cc - M /trunk/examples/c++/x11.cc - M /trunk/examples/c++/x12.cc - M /trunk/examples/c++/x14.cc - M /trunk/examples/c++/x15.cc - M /trunk/examples/c++/x16.cc - M /trunk/examples/c++/x17.cc - M /trunk/examples/c++/x18.cc - M /trunk/examples/c++/x20.cc - M /trunk/examples/c++/x21.cc - M /trunk/examples/c++/x23.cc - M /trunk/examples/d/x16d.d - M /trunk/examples/tk/xtk01.c - M /trunk/examples/tk/xtk02.c - M /trunk/examples/tk/xtk04.c - M /trunk/include/dirent_msvc.h - M /trunk/include/pdf.h + M /trunk/examples/c/x27c.c + M /trunk/examples/c++/x27.cc + M /trunk/examples/d/x27d.d + M /trunk/examples/java/x27.java M /trunk/include/qt.h - M /trunk/lib/csa/csa.c - M /trunk/lib/csa/nan.h - M /trunk/lib/nistcd/cd.c - M /trunk/lib/nn/hash.c - M /trunk/lib/nn/nan.h - M /trunk/lib/nn/nnpi.c - M /trunk/scripts/style_source.sh - M /trunk/src/ltdl_win32.c - M /trunk/src/plargs.c - M /trunk/src/plcore.c - M /trunk/src/plot3d.c - M /trunk/uncrustify.cfg - -Move from uncrustify 0.56 to 0.58. - -For this new version of uncrustify, we have regenerated -uncrustify.cfg using the following commands: - -uncrustify -c uncrustify.cfg --update-config-with-doc > new_config_file -mv new_config_file uncrustify.cfg - -0.58 does more complete processing of spaces inside casts than -was done for 0.56. So the vast majority of these source-code changes -involve inserting spaces inside casts where none appeared before. -e.g., (void*) ==> (void *) to be consistent with how, e.g., void * -is styled for spacing outside casts. - -The remaining source code changes are almost entirely due to improved -alignment processing for 0.58. - - - ------------------------------------------------------------------------- -r11759 | airwin | 2011-06-01 13:41:34 -0400 (Wed, 01 Jun 2011) | 14 lines -Changed paths: - M /trunk/bindings/f77/sccont.c - M /trunk/src/plcont.c - M /trunk/src/plimage.c - M /trunk/src/plshade.c - M /trunk/src/plvect.c - M /trunk/uncrustify.cfg - -Style changes: - -Remove whitespace just inside cast parentheses. This is the style we -already have in most cases, but force this in all cases now for -consistency. - -Force removal of any spaces between pointer stars. (i.e., "* *" ==> -"**"). This is our uniform style now in any case (i.e. it introduces -no source code changes). However, this change is needed for when (in -the immediate future) we move to uncrustify-0.58 to work around an -issue (all "**" instances were being changed to "* *" inside casts) -for that version of uncrustify. - - ------------------------------------------------------------------------- -r11758 | arjenmarkus | 2011-05-31 05:02:36 -0400 (Tue, 31 May 2011) | 4 lines -Changed paths: + M /trunk/src/plarc.c M /trunk/src/plctrl.c + M /trunk/utils/plrender.c -Introduced three macros to deal with the size of the buffers in the various functions. -Introduced a static function read_line to read a complete line from a file and store as -much of it in the buffer as will fit. The line is stripped of carriage returns, newlines -and trailing blanks, so that reading the palette files is more robust. ------------------------------------------------------------------------- -r11757 | airwin | 2011-05-30 16:23:27 -0400 (Mon, 30 May 2011) | 2 lines -Changed paths: - M /trunk/drivers/cairo.c - M /trunk/examples/c/x33c.c - M /trunk/examples/c/x34c.c - M /trunk/include/plplot.h - M /trunk/src/plctrl.c - M /trunk/src/pllegend.c - Style previous changes. ------------------------------------------------------------------------ -r11756 | airwin | 2011-05-30 16:16:51 -0400 (Mon, 30 May 2011) | 3 lines +r11934 | hezekiahcarty | 2011-09-23 09:34:31 -0400 (Fri, 23 Sep 2011) | 1 line Changed paths: - M /trunk/include/plplot.h + M /trunk/cmake/modules/ocaml.cmake -Switch to less error-prone hexadecimal notation for PL_POSITION_*, -PL_LEGEND_*, and PL_COLORBAR_* #defines. - +Re-enable OCaml by default now that the interface has been fixed ------------------------------------------------------------------------ -r11755 | airwin | 2011-05-30 15:11:52 -0400 (Mon, 30 May 2011) | 12 lines +r11933 | hezekiahcarty | 2011-09-23 09:34:23 -0400 (Fri, 23 Sep 2011) | 6 lines Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/src/pllegend.c - -Put the "m" and "n" axis_opts under user control rather than -specifying them internally within the plcolorbar code. This change -completes my goal of removing cross-talk between PL_POSITION_* bits -(now reserved for specifying only the position of the colorbar) and other -characteristics of the plcolorbar result. - -There is still a lot of work I have planned for plcolorbar. First on -that agenda is to use the same positioning logic as is used for -pllegend. This planned change is only possible because of the prior -work of removing the cross-talk mentioned above. - - ------------------------------------------------------------------------- -r11754 | hezekiahcarty | 2011-05-17 18:16:51 -0400 (Tue, 17 May 2011) | 1 line -Changed paths: - M /trunk/.gitignore - -Add the build/ directory to the list of paths ignored by git ------------------------------------------------------------------------- -r11753 | hezekiahcarty | 2011-05-17 18:16:45 -0400 (Tue, 17 May 2011) | 4 lines -Changed paths: - M /trunk/examples/c/CMakeLists.txt - A /trunk/examples/c/x34c.c - -Add a new C example 34 which illustrates the use of pl[sg]drawmode - -This example and the drawing mode functions should not be propagated to -other language bindings until they have been OK'd on the development list. ------------------------------------------------------------------------- -r11752 | hezekiahcarty | 2011-05-17 18:16:36 -0400 (Tue, 17 May 2011) | 6 lines -Changed paths: - M /trunk/drivers/cairo.c - -Add drawing mode setting/getting support for Cairo output devices - -There are a few changes in how transparent colors are handled by the xcairo -device in order to keep output consistent with the other Cairo devices. -This should not affect any of the existing examples, and it may fix/avoid -some potential rendering bugs which could come up with the xcairo device. ------------------------------------------------------------------------- -r11751 | hezekiahcarty | 2011-05-17 18:16:30 -0400 (Tue, 17 May 2011) | 9 lines -Changed paths: - M /trunk/include/plplot.h - M /trunk/include/plstrm.h - M /trunk/src/plctrl.c - -Add drawing mode setting and getting support (no driver support yet) - -These two new functions allow a user to specify different drawing modes, -such as replacing the current plot content with the drawing color, even if -the drawing color is transparent (SOURCE in Cairo) or XOR drawing. - -This is only intended to be supported by output devices which support these -operations directly. At least Cairo and Qt support the modes included in -this commit, along with several others. ------------------------------------------------------------------------- -r11750 | airwin | 2011-05-16 16:35:36 -0400 (Mon, 16 May 2011) | 4 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/include/plplot.h - M /trunk/src/pllegend.c - -User control of plcolorbar edge drawing using standard plbox "b", "c", -"u", and "w" options rather than PL_COLORBAR_NOEDGE and -PL_COLORBAR_EDGE opt bits. - ------------------------------------------------------------------------- -r11749 | airwin | 2011-05-12 16:39:42 -0400 (Thu, 12 May 2011) | 2 lines -Changed paths: - M /trunk/drivers/xwin.c - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/include/plplot.h - M /trunk/include/plxwd.h - M /trunk/src/plcore.c - M /trunk/src/plimage.c - M /trunk/src/pllegend.c - M /trunk/src/plshade.c - -Style recent changes. - ------------------------------------------------------------------------- -r11748 | airwin | 2011-05-12 16:24:26 -0400 (Thu, 12 May 2011) | 3 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/examples/c/x33c.c - M /trunk/src/pllegend.c - -Improved handling of tick marks and numerical tick labels that gives the -user more control. - ------------------------------------------------------------------------- -r11747 | airwin | 2011-05-12 16:17:40 -0400 (Thu, 12 May 2011) | 11 lines -Changed paths: - M /trunk/src/plbox.c - -If both "b" and "u" options specified for xopt or yopt argument for -plaxes (or plbox), "u" option has the priority. - -If both "c" and "w" options specified for xopt or yopt argument for -plaxes (or plbox), "w" option has the priority. - -Implement "x" option for xopt or yopt argument for plaxes (or plbox). -This option has all the side effects of "t" such as numerical tick -labelling (if specified), but the actual ticks are not drawn. - - ------------------------------------------------------------------------- -r11746 | andrewross | 2011-05-06 16:24:10 -0400 (Fri, 06 May 2011) | 3 lines -Changed paths: - M /trunk/drivers/xwin.c - M /trunk/include/plxwd.h - -Changes to xwin driver to cache the background colour of the page so colour is correct if page is resized / redrawn. - - ------------------------------------------------------------------------- -r11745 | andrewross | 2011-05-06 16:00:50 -0400 (Fri, 06 May 2011) | 3 lines -Changed paths: - M /trunk/drivers/xwin.c - -Fix another spelling mistake in comment. - - ------------------------------------------------------------------------- -r11744 | andrewross | 2011-05-06 15:14:16 -0400 (Fri, 06 May 2011) | 3 lines -Changed paths: - M /trunk/drivers/aqt.c - M /trunk/drivers/xwin.c - -Fix a couple of typos in comments. - - ------------------------------------------------------------------------- -r11743 | andrewross | 2011-05-04 14:38:51 -0400 (Wed, 04 May 2011) | 3 lines -Changed paths: - M /trunk/drivers/xwin.c - -Explicitly set background colour in plD_bop_xw (consistent with other devices) so that example 33 works as expected. - - ------------------------------------------------------------------------- -r11742 | airwin | 2011-05-01 20:59:06 -0400 (Sun, 01 May 2011) | 5 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Move back to cmap1_blue_red.pal since that cmap1 shows interesting -abrupt changes for the end cap colours. Since one of those end cap -colours is black, change the background of the -colorbar pages to -an unsaturated green to contrast with that black colour. - ------------------------------------------------------------------------- -r11741 | airwin | 2011-05-01 16:08:03 -0400 (Sun, 01 May 2011) | 9 lines -Changed paths: - M /trunk/examples/c/x16c.c - M /trunk/include/plplot.h - M /trunk/src/pllegend.c - -Control whether edges of colorbar box and caps are drawn using the -PL_COLORBAR_(NOEDGE, EDGE) opt bits. The default is -PL_COLORBAR_NOEDGE. For usage where the background color is not -included in the color range (such as example 33) PL_COLORBAR_NOEDGE -makes a nicer looking result. For usage where the background colour -is included in the color range (such as example 16) PL_COLORBAR_EDGE -makes a nicer looking result. - - ------------------------------------------------------------------------- -r11740 | airwin | 2011-05-01 15:32:54 -0400 (Sun, 01 May 2011) | 6 lines -Changed paths: - M /trunk/examples/c/x33c.c - -Use different cmap1 color scheme that does not have max or min colour -equal to the background. This gets rid of the "empty" cap case (where -cap colour is the same as the background colour) that looks like an -error. - - ------------------------------------------------------------------------- -r11739 | airwin | 2011-05-01 15:27:20 -0400 (Sun, 01 May 2011) | 6 lines -Changed paths: - M /trunk/doc/docbook/src/api.xml - M /trunk/src/plbox.c - -Add "u" (exactly like "b" except don't draw edge line) and "w" -(exactly like "c" except don't draw edge line) options for xopt and -yopt. These new "u" and "w" options are especially useful for -plcolorbar where often the user does not want an edge line. - - ------------------------------------------------------------------------- -r11738 | airwin | 2011-05-01 15:14:40 -0400 (Sun, 01 May 2011) | 3 lines -Changed paths: - M /trunk/src/plgradient.c - -Comment out line draw which was acting as a visual debugging cue for -the direction of the gradient. - ------------------------------------------------------------------------- -r11737 | airwin | 2011-04-30 15:11:44 -0400 (Sat, 30 Apr 2011) | 5 lines -Changed paths: - M /trunk/include/plplotP.h - M /trunk/src/plbox.c - -Specify prototype for label_box_custom rather than using default -prototype. Hide this function from external use by _not_ specifying -PLDLLIMPEXP qualifier. - - ------------------------------------------------------------------------- -r11736 | airwin | 2011-04-30 14:37:28 -0400 (Sat, 30 Apr 2011) | 21 lines -Changed paths: - M /trunk/src/pllegend.c - -Put the orientation of the colorbar directly under the control of the -user with the PL_COLORBAR_ORIENT_(RIGHT, TOP, LEFT, BOTTOM) orientation bits of -opt. However, if the user does not specify any of these bits, then adopt -a sensible orientation default which depends on position. - -Make all previous orientation logic (which was controlled strictly by -position bits before) depend on the orientation bits instead. - -There are no changes to the example 33 PostScript results due to these -internal changes (because of the default orientation choice noted -above). - -ToDo: My goal here is that position should control nothing except -overall position of colorbar with no cross-talk with how that colorbar -object is specified except for the default value of the orientation. -I have only dealt with the obvious orientation stuff for now and there -is some non-position logic (e.g., label offsets, numerical label -positions, and tick marks for the colorbar) that currently depends on -position bits that still must be dealt with to achieve my goal. - - ------------------------------------------------------------------------- -r11735 | airwin | 2011-04-30 00:28:20 -0400 (Sat, 30 Apr 2011) | 4 lines -Changed paths: - D /trunk/examples/perl/plplot.pd.patch - -This patch not needed with PDL-Graphics-PLplot-0.55 which is the only -version of PDL-Graphics-PLplot which we accept for testing. Therefore, -remove this patch. - ------------------------------------------------------------------------- -r11734 | airwin | 2011-04-30 00:22:46 -0400 (Sat, 30 Apr 2011) | 8 lines -Changed paths: - M /trunk/examples/perl/CMakeLists.txt - M /trunk/plplot_test/test_pdl.sh.in - -Add example 33 to Perl/PDL examples tests. - -Drop all PDL::Graphics::PLplot version logic for choice of examples. -Instead use a... [truncated message content] |