# Just Launched: You can now import projects and releases from Google Code onto SourceForge

We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps.

## plplot-cvs — For PLplot svn commit messages

You can subscribe to this list here.

2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 Jan Feb Mar Apr May (33) Jun Jul (30) Aug (2) Sep Oct (30) Nov (136) Dec (59) Jan (255) Feb (169) Mar (322) Apr (185) May (33) Jun (89) Jul (47) Aug (59) Sep (40) Oct (31) Nov (74) Dec (84) Jan (163) Feb (78) Mar (23) Apr (5) May (22) Jun (75) Jul (143) Aug (48) Sep (111) Oct (58) Nov (124) Dec (278) Jan (106) Feb (276) Mar (354) Apr (97) May (14) Jun (3) Jul (7) Aug (21) Sep (83) Oct (110) Nov (3) Dec (119) Jan (318) Feb (409) Mar (68) Apr (23) May (105) Jun (147) Jul (69) Aug (53) Sep (23) Oct (14) Nov (15) Dec (63) Jan (146) Feb (69) Mar (157) Apr (127) May (166) Jun (8) Jul (5) Aug (3) Sep (8) Oct (17) Nov (29) Dec (34) Jan (3) Feb (4) Mar (1) Apr (70) May (241) Jun (82) Jul (344) Aug (196) Sep (87) Oct (57) Nov (121) Dec (86) Jan (60) Feb (67) Mar (102) Apr (28) May (13) Jun (29) Jul (38) Aug (56) Sep (91) Oct (89) Nov (50) Dec (68) Jan (87) Feb (47) Mar (100) Apr (34) May (65) Jun (54) Jul (98) Aug (128) Sep (109) Oct (141) Nov (40) Dec (206) Jan (176) Feb (226) Mar (134) Apr (84) May (152) Jun (85) Jul (91) Aug (153) Sep (141) Oct (59) Nov (87) Dec (75) Jan (58) Feb (41) Mar (51) Apr (74) May (81) Jun (39) Jul (30) Aug (43) Sep (76) Oct (59) Nov (62) Dec (52) Jan (125) Feb (41) Mar (96) Apr (53) May (21) Jun (23) Jul (48) Aug (71) Sep (37) Oct (81) Nov (60) Dec (32) Jan (51) Feb (23) Mar Apr (8) May (2) Jun Jul (8) Aug (25) Sep (4) Oct (32) Nov (17) Dec (2) Jan (8) Feb (2) Mar (9) Apr (9) May (37) Jun (48) Jul (63) Aug (42) Sep (59) Oct (83) Nov (141) Dec (133) Jan (57) Feb (58) Mar (18) Apr May Jun Jul Aug Sep Oct Nov Dec
S M T W T F S

1
(3)
2
(1)
3
(5)
4
(6)
5

6

7

8

9
(5)
10

11

12
(2)
13
(1)
14
(1)
15

16
(2)
17

18
(1)
19
(3)
20
(3)
21
(2)
22

23

24
(3)
25

26

27
(1)
28
(1)
29

30
(2)
31

Showing 5 results of 5

 [Plplot-cvs] SF.net SVN: plplot:[12479] trunk/doc/docbook/src/CMakeLists.txt From: - 2013-08-09 23:38:31 Revision: 12479 http://sourceforge.net/p/plplot/code/12479 Author: airwin Date: 2013-08-09 23:38:29 +0000 (Fri, 09 Aug 2013) Log Message: ----------- Remove \$ENV{DESTDIR} references from install(CODE...) commands and also reformat those commands to make them more human-readable. Note, these are all examples of where file(INSTALL...) is used inside install(CODE...). According to the documentation file(INSTALL...) is the workhorse signature normall used for install commands so it is reasonable to infer that file(INSTALL...) already does its own \$ENV{DESTDIR} handling. Anyhow, it turns out our own use of \$ENV{DESTDIR} is redundant and causes an error (double use of DESTDIR for the docbook documentation) found by Orion Poplawski and which I have confirmed. Note, for all other uses of install(CODE...) that does not have a call to file(INSTALL...) inside the code fragment (e.g., doc/CMakeLists.txt) it is necessary to use \$ENV{DESTDIR}. Tested by Alan W. Irwin using the cmake options -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_DOC=ON -DBUILD_DOX_DOC=ON and "make -j4 DESTDIR=tmp install >& install.out". The resulting files (including both doxgen-generated ones and docbook-generated ones) were all installed to tmp/usr/... in the build_tree with no double use of DESTDIR and no attempt to install files to /usr. Modified Paths: -------------- trunk/doc/docbook/src/CMakeLists.txt Modified: trunk/doc/docbook/src/CMakeLists.txt =================================================================== --- trunk/doc/docbook/src/CMakeLists.txt 2013-08-09 22:40:34 UTC (rev 12478) +++ trunk/doc/docbook/src/CMakeLists.txt 2013-08-09 23:38:29 UTC (rev 12479) @@ -492,8 +492,14 @@ # command. This makes for slightly ugly looking code. if(BUILD_HTML OR PREBUILT_DOC) - install(CODE "file(GLOB HTML_FILES ${CMAKE_CURRENT_BINARY_DIR}/*.${HTML_EXT})\n foreach(file \${HTML_FILES}) \n file(INSTALL DESTINATION \$ENV{DESTDIR}${DOC_DIR}/html TYPE FILE FILES \"\${file}\") \n endforeach (file \"\${HTML_FILES}\")") install(FILES${CMAKE_CURRENT_BINARY_DIR}/${HTML_MANIFEST} stylesheet.css DESTINATION${DOC_DIR}/html ) + install(CODE " +file(GLOB HTML_FILES ${CMAKE_CURRENT_BINARY_DIR}/*.${HTML_EXT}) +foreach(file \${HTML_FILES}) + file(INSTALL DESTINATION${DOC_DIR}/html TYPE FILE FILES \"\${file}\") +endforeach (file \"\${HTML_FILES}\") +" + ) endif(BUILD_HTML OR PREBUILT_DOC) if(BUILD_PRINT OR PREBUILT_DOC) @@ -501,13 +507,25 @@ endif(BUILD_PRINT OR PREBUILT_DOC) if(BUILD_MAN OR PREBUILT_DOC) - install(CODE "file(GLOB MAN_FILES ${CMAKE_CURRENT_BINARY_DIR}/*.${MANVOL})\n foreach(file \${MAN_FILES}) \n file(INSTALL DESTINATION \$ENV{DESTDIR}${MAN_DIR}/man3 TYPE FILE FILES \"\${file}\") \n endforeach (file \"\${MAN_FILES}\")") -# install(FILES${CMAKE_CURRENT_BINARY_DIR}/${MAN_MANIFEST} DESTINATION${MAN_DIR}/man3 ) + #install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${MAN_MANIFEST} DESTINATION ${MAN_DIR}/man3 ) + install(CODE " +file(GLOB MAN_FILES${CMAKE_CURRENT_BINARY_DIR}/*.${MANVOL}) +foreach(file \${MAN_FILES}) + file(INSTALL DESTINATION ${MAN_DIR}/man3 TYPE FILE FILES \"\${file}\") +endforeach(file \"\${MAN_FILES}\") +" + ) endif(BUILD_MAN OR PREBUILT_DOC) if(BUILD_INFO OR PREBUILT_DOC) - install(CODE "file(GLOB INFO_FILES${CMAKE_CURRENT_BINARY_DIR}/*.info*)\n foreach(file \${INFO_FILES}) \n file(INSTALL DESTINATION \$ENV{DESTDIR}${INFO_DIR} TYPE FILE FILES \"\${file}\") \n endforeach (file \"\${INFO_FILES}\")") -# install(FILES${CMAKE_CURRENT_BINARY_DIR}/${INFO_MANIFEST} DESTINATION${INFO_DIR} ) + #install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${INFO_MANIFEST} DESTINATION ${INFO_DIR} ) + install(CODE " +file(GLOB INFO_FILES${CMAKE_CURRENT_BINARY_DIR}/*.info*) +foreach(file \${INFO_FILES}) + file(INSTALL DESTINATION${INFO_DIR} TYPE FILE FILES \"\${file}\") +endforeach (file \"\${INFO_FILES}\") +" + ) endif(BUILD_INFO OR PREBUILT_DOC) # Everything below here has to do with the custom target www-install This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. 
 [Plplot-cvs] SF.net SVN: plplot:[12478] trunk/doc/Doxyfile.in From: - 2013-08-09 22:40:37 Revision: 12478 http://sourceforge.net/p/plplot/code/12478 Author: airwin Date: 2013-08-09 22:40:34 +0000 (Fri, 09 Aug 2013) Log Message: ----------- Exclude bindings/python/plplot.py (the user-friendly python interface to PLplot) from doxygen consideration. For an unknown reason, that file (which includes no specific doxygen commands) generates a doxgyen segfault. Modified Paths: -------------- trunk/doc/Doxyfile.in Modified: trunk/doc/Doxyfile.in =================================================================== --- trunk/doc/Doxyfile.in 2013-08-09 21:41:36 UTC (rev 12477) +++ trunk/doc/Doxyfile.in 2013-08-09 22:40:34 UTC (rev 12478) @@ -707,7 +707,9 @@ EXCLUDE = "@CMAKE_BINARY_DIR@/bindings/f77/plplot_parameters.h" \ "@CMAKE_SOURCE_DIR@/bindings/f95/plplot_parameters.h" \ - "@CMAKE_BINARY_DIR@/bindings/f95/plplot_parameters.h" + "@CMAKE_BINARY_DIR@/bindings/f95/plplot_parameters.h" \ + "@CMAKE_SOURCE_DIR@/bindings/python/plplot.py" \ + "@CMAKE_BINARY_DIR@/bindings/python/plplot.py" # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or # directories that are symbolic links (a Unix file system feature) are excluded This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. 
 [Plplot-cvs] SF.net SVN: plplot:[12477] trunk/doc/Doxyfile.in From: - 2013-08-09 21:41:41 Revision: 12477 http://sourceforge.net/p/plplot/code/12477 Author: airwin Date: 2013-08-09 21:41:36 +0000 (Fri, 09 Aug 2013) Log Message: ----------- Update from Doxyfile 1.7.1 to Doxyfile 1.8.1.2 using the "doxygen -u" command. Note, this update of the configuration file to be consistent with my doxygen version did not get rid of a segfault that has been introduced by some fairly recent change (either in my doxygen version or in our code). Modified Paths: -------------- trunk/doc/Doxyfile.in Modified: trunk/doc/Doxyfile.in =================================================================== --- trunk/doc/Doxyfile.in 2013-08-09 16:48:32 UTC (rev 12476) +++ trunk/doc/Doxyfile.in 2013-08-09 21:41:36 UTC (rev 12477) @@ -1,14 +1,14 @@ -# Doxyfile 1.7.1 +# Doxyfile 1.8.1.2 # This file describes the settings to be used by the documentation system -# doxygen (www.doxygen.org) for a project +# doxygen (www.doxygen.org) for a project. # -# All text after a hash (#) is considered a comment and will be ignored +# All text after a hash (#) is considered a comment and will be ignored. # The format is: # TAG = value [value, ...] # For lists items can also be appended using: # TAG += value [value, ...] -# Values that contain spaces should be placed between quotes (" ") +# Values that contain spaces should be placed between quotes (" "). #--------------------------------------------------------------------------- # Project related configuration options @@ -22,8 +22,9 @@ DOXYFILE_ENCODING = UTF-8 -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded -# by quotes) that should identify the project. +# The PROJECT_NAME tag is a single word (or sequence of words) that should +# identify the project. Note that if you do not use Doxywizard you need +# to put quotes around the project name if it contains spaces. PROJECT_NAME = PLplot @@ -33,6 +34,19 @@ PROJECT_NUMBER = @VERSION@ +# Using the PROJECT_BRIEF tag one can provide an optional one line description +# for a project that appears at the top of each page and should give viewer +# a quick idea about the purpose of the project. Keep the description short. + +PROJECT_BRIEF = + +# With the PROJECT_LOGO tag one can specify an logo or icon that is +# included in the documentation. The maximum height of the logo should not +# exceed 55 pixels and the maximum width should not exceed 200 pixels. +# Doxygen will copy the logo to the output directory. + +PROJECT_LOGO = + # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # base path where the generated documentation will be put. # If a relative path is entered, it will be relative to the location @@ -57,7 +71,7 @@ # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, -# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, +# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. OUTPUT_LANGUAGE = English @@ -126,7 +140,7 @@ STRIP_FROM_INC_PATH = # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter -# (but less readable) file names. This can be useful is your file systems +# (but less readable) file names. This can be useful if your file system # doesn't support long names like on DOS, Mac, or CD-ROM. SHORT_NAMES = NO @@ -181,6 +195,13 @@ ALIASES = +# This tag can be used to specify a number of word-keyword mappings (TCL only). +# A mapping has the form "name=value". For example adding +# "class=itcl::class" will allow you to use the command class in the +# itcl::class meaning. + +TCL_SUBST = + # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C # sources only. Doxygen will then generate output that is more tailored for C. # For instance, some of the names that are used will be different. The list @@ -219,11 +240,20 @@ EXTENSION_MAPPING = +# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all +# comments according to the Markdown format, which allows for more readable +# documentation. See http://daringfireball.net/projects/markdown/ for details. +# The output of markdown processing is further processed by doxygen, so you +# can mix doxygen, HTML, and XML commands with Markdown formatting. +# Disable only in case of backward compatibilities issues. + +MARKDOWN_SUPPORT = YES + # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should # set this tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. -# func(std::string) {}). This also make the inheritance and collaboration +# func(std::string) {}). This also makes the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. BUILTIN_STL_SUPPORT = NO @@ -241,7 +271,7 @@ # For Microsoft's IDL there are propget and propput attributes to indicate getter # and setter methods for a property. Setting this option to YES (the default) -# will make doxygen to replace the get and set methods by a property in the +# will make doxygen replace the get and set methods by a property in the # documentation. This will only work if the methods are indeed getting or # setting a simple type. If this is not the case, or you want to show the # methods anyway, you should set this option to NO. @@ -263,6 +293,22 @@ SUBGROUPING = YES +# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and +# unions are shown inside the group in which they are included (e.g. using +# @ingroup) instead of on a separate page (for HTML and Man pages) or +# section (for LaTeX and RTF). + +INLINE_GROUPED_CLASSES = NO + +# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and +# unions with only public data fields will be shown inline in the documentation +# of the scope in which they are defined (i.e. file, namespace, or group +# documentation), provided this scope is documented. If set to NO (the default), +# structs, classes, and unions are shown on a separate page (for HTML and Man +# pages) or section (for LaTeX and RTF). + +INLINE_SIMPLE_STRUCTS = NO + # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum # is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct @@ -279,16 +325,27 @@ # For small to medium size projects (<1000 input files) the default value is # probably good enough. For larger projects a too small cache size can cause # doxygen to be busy swapping symbols to and from disk most of the time -# causing a significant performance penality. +# causing a significant performance penalty. # If the system has enough physical memory increasing the cache will improve the # performance by keeping more symbols in memory. Note that the value works on -# a logarithmic scale so increasing the size by one will rougly double the +# a logarithmic scale so increasing the size by one will roughly double the # memory usage. The cache size is given by this formula: # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, -# corresponding to a cache size of 2^16 = 65536 symbols +# corresponding to a cache size of 2^16 = 65536 symbols. SYMBOL_CACHE_SIZE = 0 +# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be +# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given +# their name and scope. Since this can be an expensive process and often the +# same symbol appear multiple times in the code, doxygen keeps a cache of +# pre-resolved symbols. If the cache is too small doxygen will become slower. +# If the cache is too large, memory is wasted. The cache size is given by this +# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, +# corresponding to a cache size of 2^16 = 65536 symbols. + +LOOKUP_CACHE_SIZE = 0 + #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- @@ -305,6 +362,10 @@ EXTRACT_PRIVATE = YES +# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. + +EXTRACT_PACKAGE = NO + # If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. @@ -327,7 +388,7 @@ # extracted and appear in the documentation as a namespace called # 'anonymous_namespace{file}', where file will be replaced with the base # name of the file that contains the anonymous namespace. By default -# anonymous namespace are hidden. +# anonymous namespaces are hidden. EXTRACT_ANON_NSPACES = NO @@ -438,6 +499,15 @@ SORT_BY_SCOPE_NAME = NO +# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to +# do proper type resolution of all parameters of a function it will reject a +# match between the prototype and the implementation of a member function even +# if there is only one candidate or it is obvious which candidate to choose +# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen +# will still accept a match between prototype and implementation in such cases. + +STRICT_PROTO_MATCHING = NO + # The GENERATE_TODOLIST tag can be used to enable (YES) or # disable (NO) the todo list. This list is created by putting \todo # commands in the documentation. @@ -468,10 +538,10 @@ ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines -# the initial value of a variable or define consists of for it to appear in +# the initial value of a variable or macro consists of for it to appear in # the documentation. If the initializer consists of more lines than specified # here it will be hidden. Use a value of 0 to hide initializers completely. -# The appearance of the initializer of individual variables and defines in the +# The appearance of the initializer of individual variables and macros in the # documentation can be controlled using \showinitializer or \hideinitializer # command in the documentation regardless of this setting. @@ -483,12 +553,6 @@ SHOW_USED_FILES = YES -# If the sources in your project are distributed over multiple directories -# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy -# in the documentation. The default is NO. - -SHOW_DIRECTORIES = NO - # Set the SHOW_FILES tag to NO to disable the generation of the Files page. # This will remove the Files entry from the Quick Index and from the # Folder Tree View (if specified). The default is YES. @@ -514,13 +578,23 @@ # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed # by doxygen. The layout file controls the global structure of the generated -# output files in an output format independent way. The create the layout file +# output files in an output format independent way. To create the layout file # that represents doxygen's defaults, run doxygen with the -l option. # You can optionally specify a file name after the option, if omitted # DoxygenLayout.xml will be used as the name of the layout file. LAYOUT_FILE = +# The CITE_BIB_FILES tag can be used to specify one or more bib files +# containing the references data. This must be a list of .bib files. The +# .bib extension is automatically appended if omitted. Using this command +# requires the bibtex tool to be installed. See also +# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style +# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this +# feature you need bibtex and perl available in the search path. + +CITE_BIB_FILES = + #--------------------------------------------------------------------------- # configuration options related to warning and progress messages #--------------------------------------------------------------------------- @@ -549,7 +623,7 @@ WARN_IF_DOC_ERROR = YES -# This WARN_NO_PARAMDOC option can be abled to get warnings for +# The WARN_NO_PARAMDOC option can be enabled to get warnings for # functions that are documented, but have no documentation for their parameters # or return value. If set to NO (the default) doxygen will only warn about # wrong or incomplete parameter documentation, but not about the absence of @@ -581,16 +655,15 @@ # directories like "/usr/src/myproject". Separate the files or directories # with spaces. -INPUT = \ - "@CMAKE_SOURCE_DIR@/lib" \ - "@CMAKE_SOURCE_DIR@/src" \ +INPUT = "@CMAKE_SOURCE_DIR@/lib" \ + "@CMAKE_SOURCE_DIR@/src" \ "@CMAKE_SOURCE_DIR@/drivers" \ "@CMAKE_SOURCE_DIR@/bindings" \ "@CMAKE_SOURCE_DIR@/include" \ "@CMAKE_BINARY_DIR@/config.h" \ "@CMAKE_BINARY_DIR@/lib" \ "@CMAKE_BINARY_DIR@/bindings" \ - "@CMAKE_BINARY_DIR@/include" \ + "@CMAKE_BINARY_DIR@/include" # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is @@ -604,10 +677,10 @@ # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp # and *.h) to filter out the source-files in the directories. If left # blank the following patterns are tested: -# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx -# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 +# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh +# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py +# *.f90 *.f *.for *.vhd *.vhdl -# Only process C, C++, D, Java, Python, and Fortran files. FILE_PATTERNS = *.c \ *.cc \ *.cxx \ @@ -618,7 +691,7 @@ *.h \ *.py \ *.f90 \ - *.f \ + *.f # The RECURSIVE tag can be used to turn specify whether or not subdirectories # should be searched for input files as well. Possible values are YES and NO. @@ -626,20 +699,18 @@ RECURSIVE = YES -# The EXCLUDE tag can be used to specify files and/or directories that should +# The EXCLUDE tag can be used to specify files and/or directories that should be # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. +# Note that relative paths are relative to the directory from which doxygen is +# run. -# These files are Fortran, but their extension confuses doxygen -# into thinking they are C/C++ headers so exclude them as a workaround. -EXCLUDE = \ - "@CMAKE_BINARY_DIR@/bindings/f77/plplot_parameters.h" \ +EXCLUDE = "@CMAKE_BINARY_DIR@/bindings/f77/plplot_parameters.h" \ "@CMAKE_SOURCE_DIR@/bindings/f95/plplot_parameters.h" \ - "@CMAKE_BINARY_DIR@/bindings/f95/plplot_parameters.h" \ - + "@CMAKE_BINARY_DIR@/bindings/f95/plplot_parameters.h" -# The EXCLUDE_SYMLINKS tag can be used select whether or not files or -# directories that are symbolic links (a Unix filesystem feature) are excluded +# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or +# directories that are symbolic links (a Unix file system feature) are excluded # from the input. EXCLUDE_SYMLINKS = NO @@ -650,9 +721,8 @@ # against the file with absolute path, so to exclude all test directories # for example use the pattern */test/* -# Ignore .svn directories in the source tree and CMakeFiles directories -# in the build tree. -EXCLUDE_PATTERNS = */.svn/* */CMakeFiles/* +EXCLUDE_PATTERNS = */.svn/* \ + */CMakeFiles/* # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the @@ -705,8 +775,8 @@ # filter if there is a match. # The filters are a list of the form: # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further -# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER -# is applied to all files. +# info on how filters are used. If FILTER_PATTERNS is empty or if +# non of the patterns match the file name, INPUT_FILTER is applied. FILTER_PATTERNS = @@ -716,6 +786,14 @@ FILTER_SOURCE_FILES = NO +# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file +# pattern. A pattern will override the setting for FILTER_PATTERN (if any) +# and it is also possible to disable source filtering for a specific pattern +# using *.ext= (so without naming a filter). This option only has effect when +# FILTER_SOURCE_FILES is enabled. + +FILTER_SOURCE_PATTERNS = + #--------------------------------------------------------------------------- # configuration options related to source browsing #--------------------------------------------------------------------------- @@ -734,7 +812,7 @@ # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct # doxygen to hide any special comment blocks from generated source code -# fragments. Normal C and C++ comments will always remain visible. +# fragments. Normal C, C++ and Fortran comments will always remain visible. STRIP_CODE_COMMENTS = YES @@ -818,7 +896,14 @@ # The HTML_HEADER tag can be used to specify a personal HTML header for # each generated HTML page. If it is left blank doxygen will generate a -# standard header. +# standard header. Note that when using a custom header you are responsible +# for the proper inclusion of any scripts and style sheets that doxygen +# needs, which is dependent on the configuration options used. +# It is advised to generate a default header using "doxygen -w html +# header.html footer.html stylesheet.css YourConfigFile" and then modify +# that header. Note that the header is subject to change so you typically +# have to redo this when upgrading to a newer version of doxygen or when +# changing the value of configuration settings such as GENERATE_TREEVIEW! HTML_HEADER = @@ -833,12 +918,21 @@ # fine-tune the look of the HTML output. If the tag is left blank doxygen # will generate a default style sheet. Note that doxygen will try to copy # the style sheet file to the HTML output directory, so don't put your own -# stylesheet in the HTML output directory as well, or it will be erased! +# style sheet in the HTML output directory as well, or it will be erased! HTML_STYLESHEET = +# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or +# other source files which should be copied to the HTML output directory. Note +# that these files will be copied to the base HTML output directory. Use the +# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these +# files. In the HTML_STYLESHEET file, use the file name only. Also note that +# the files will be copied as-is; there are no commands or markers available. + +HTML_EXTRA_FILES = + # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. -# Doxygen will adjust the colors in the stylesheet and background images +# Doxygen will adjust the colors in the style sheet and background images # according to this color. Hue is specified as an angle on a colorwheel, # see http://en.wikipedia.org/wiki/Hue for more information. # For instance the value 0 represents red, 60 is yellow, 120 is green, @@ -868,20 +962,23 @@ HTML_TIMESTAMP = YES -# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, -# files or namespaces will be aligned in HTML using tables. If set to -# NO a bullet list will be used. - -HTML_ALIGN_MEMBERS = YES - # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the -# page has loaded. For this to work a browser that supports -# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox -# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). +# page has loaded. HTML_DYNAMIC_SECTIONS = NO +# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of +# entries shown in the various tree structured indices initially; the user +# can expand and collapse entries dynamically later on. Doxygen will expand +# the tree to such a level that at most the specified number of entries are +# visible (unless a fully collapsed tree already exceeds this amount). +# So setting the number of entries 1 will produce a full collapsed tree by +# default. 0 is a special value representing an infinite number of entries +# and will result in a full expanded tree by default. + +HTML_INDEX_NUM_ENTRIES = 100 + # If the GENERATE_DOCSET tag is set to YES, additional index files # will be generated that can be used as input for Apple's Xcode 3 # integrated development environment, introduced with OSX 10.5 (Leopard). @@ -1033,17 +1130,14 @@ ECLIPSE_DOC_ID = org.doxygen.Project -# The DISABLE_INDEX tag can be used to turn on/off the condensed index at -# top of each HTML page. The value NO (the default) enables the index and -# the value YES disables it. +# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) +# at top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. Since the tabs have the same information as the +# navigation tree you can set this option to NO if you already set +# GENERATE_TREEVIEW to YES. DISABLE_INDEX = NO -# This tag can be used to set the number of enum values (range [1..20]) -# that doxygen will group on one line in the generated HTML documentation. - -ENUM_VALUES_PER_LINE = 4 - # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. # If the tag value is set to YES, a side panel will be generated @@ -1051,13 +1145,17 @@ # is generated for HTML Help). For this to work a browser that supports # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). # Windows users are probably better off using the HTML help feature. +# Since the tree basically has the same information as the tab index you +# could consider to set DISABLE_INDEX to NO when enabling this option. GENERATE_TREEVIEW = YES -# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, -# and Class Hierarchy pages using a tree view instead of an ordered list. +# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values +# (range [0,1..20]) that doxygen will group on one line in the generated HTML +# documentation. Note that a value of 0 will completely suppress the enum +# values from appearing in the overview section. -USE_INLINE_TREES = NO +ENUM_VALUES_PER_LINE = 4 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be # used to set the initial width (in pixels) of the frame in which the tree @@ -1086,6 +1184,32 @@ FORMULA_TRANSPARENT = YES +# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax +# (see http://www.mathjax.org) which uses client side Javascript for the +# rendering instead of using prerendered bitmaps. Use this if you do not +# have LaTeX installed or if you want to formulas look prettier in the HTML +# output. When enabled you may also need to install MathJax separately and +# configure the path to it using the MATHJAX_RELPATH option. + +USE_MATHJAX = NO + +# When MathJax is enabled you need to specify the location relative to the +# HTML output directory using the MATHJAX_RELPATH option. The destination +# directory should contain the MathJax.js script. For instance, if the mathjax +# directory is located at the same level as the HTML output directory, then +# MATHJAX_RELPATH should be ../mathjax. The default value points to +# the MathJax Content Delivery Network so you can quickly see the result without +# installing MathJax. +# However, it is strongly recommended to install a local +# copy of MathJax from http://www.mathjax.org before deployment. + +MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest + +# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension +# names that should be enabled during MathJax rendering. + +MATHJAX_EXTENSIONS = + # When the SEARCHENGINE tag is enabled doxygen will generate a search box # for the HTML output. The underlying search engine uses javascript # and DHTML and should work on any modern browser. Note that when using @@ -1101,7 +1225,7 @@ # using Javascript. Doxygen will generate the search PHP script and index # file to put on the web server. The advantage of the server # based approach is that it scales better to large projects and allows -# full text search. The disadvances is that it is more difficult to setup +# full text search. The disadvantages are that it is more difficult to setup # and does not have live searching capabilities. SERVER_BASED_SEARCH = NO @@ -1142,7 +1266,7 @@ COMPACT_LATEX = NO # The PAPER_TYPE tag can be used to set the paper type that is used -# by the printer. Possible values are: a4, a4wide, letter, legal and +# by the printer. Possible values are: a4, letter, legal and # executive. If left blank a4wide will be used. PAPER_TYPE = a4wide @@ -1159,6 +1283,13 @@ LATEX_HEADER = +# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for +# the generated latex document. The footer should contain everything after +# the last chapter. If it is left blank doxygen will generate a +# standard footer. Notice: only use this tag if you know what you are doing! + +LATEX_FOOTER = + # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated # is prepared for conversion to pdf (using ps2pdf). The pdf file will # contain links (just like the HTML output) instead of page references @@ -1192,6 +1323,12 @@ LATEX_SOURCE_CODE = NO +# The LATEX_BIB_STYLE tag can be used to specify the style to use for the +# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See +# http://en.wikipedia.org/wiki/BibTeX for more info. + +LATEX_BIB_STYLE = plain + #--------------------------------------------------------------------------- # configuration options related to the RTF output #--------------------------------------------------------------------------- @@ -1223,7 +1360,7 @@ RTF_HYPERLINKS = NO -# Load stylesheet definitions from file. Syntax is similar to doxygen's +# Load style sheet definitions from file. Syntax is similar to doxygen's # config file, i.e. a series of assignments. You only have to provide # replacements, missing definitions are set to their default value. @@ -1368,7 +1505,7 @@ EXPAND_ONLY_PREDEF = NO # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files -# in the INCLUDE_PATH (see below) will be search if a #include is found. +# pointed to by INCLUDE_PATH will be searched when a #include is found. SEARCH_INCLUDES = YES @@ -1376,8 +1513,6 @@ # contain include files that are not input files but should be processed by # the preprocessor. -# Work around a doxygen bug in finding build_tree/bindings/tcl/tclgen_s.h even -# though the corresponding directory is recursively part of input. INCLUDE_PATH = @CMAKE_BINARY_DIR@/bindings/tcl # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard @@ -1400,15 +1535,15 @@ # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then # this tag can be used to specify a list of macro names that should be expanded. # The macro definition that is found in the sources will be used. -# Use the PREDEFINED tag if you want to use a different macro definition. +# Use the PREDEFINED tag if you want to use a different macro definition that +# overrules the definition found in the source code. EXPAND_AS_DEFINED = # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then -# doxygen's preprocessor will remove all function-like macros that are alone -# on a line, have an all uppercase name, and do not end with a semicolon. Such -# function macros are typically used for boiler-plate code, and will confuse -# the parser if not removed. +# doxygen's preprocessor will remove all references to function-like macros +# that are alone on a line, have an all uppercase name, and do not end with a +# semicolon, because these will confuse the parser if not removed. SKIP_FUNCTION_MACROS = YES @@ -1416,22 +1551,18 @@ # Configuration::additions related to external references #--------------------------------------------------------------------------- -# The TAGFILES option can be used to specify one or more tagfiles. -# Optionally an initial location of the external documentation -# can be added for each tagfile. The format of a tag file without -# this location is as follows: +# The TAGFILES option can be used to specify one or more tagfiles. For each +# tag file the location of the external documentation should be added. The +# format of a tag file without this location is as follows: # # TAGFILES = file1 file2 ... # Adding location for the tag files is done as follows: # # TAGFILES = file1=loc1 "file2 = loc2" ... -# where "loc1" and "loc2" can be relative or absolute paths or -# URLs. If a location is present for each tag, the installdox tool -# does not have to be run to correct the links. -# Note that each tag file must have a unique name -# (where the name does NOT include the path) -# If a tag file is not located in the directory in which doxygen -# is run, you must also specify the path to the tagfile here. +# where "loc1" and "loc2" can be relative or absolute paths +# or URLs. Note that each tag file must have a unique name (where the name does +# NOT include the path). If a tag file is not located in the directory in which +# doxygen is run, you must also specify the path to the tagfile here. TAGFILES = @@ -1464,9 +1595,8 @@ # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base # or super classes. Setting the tag to NO turns the diagrams off. Note that -# this option is superseded by the HAVE_DOT option below. This is only a -# fallback. It is recommended to install and use dot, since it yields more -# powerful graphs. +# this option also works with HAVE_DOT disabled, but it is recommended to +# install and use dot, since it yields more powerful graphs. CLASS_DIAGRAMS = YES @@ -1500,14 +1630,12 @@ DOT_NUM_THREADS = 0 -# By default doxygen will write a font called FreeSans.ttf to the output -# directory and reference it in all dot files that doxygen generates. This -# font does not include all possible unicode characters however, so when you need -# these (or just want a differently looking font) you can specify the font name -# using DOT_FONTNAME. You need need to make sure dot is able to find the font, -# which can be done by putting it in a standard location or by setting the -# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory -# containing the font. +# By default doxygen will use the Helvetica font for all dot files that +# doxygen generates. When you want a differently looking font you can specify +# the font name using DOT_FONTNAME. You need to make sure dot is able to find +# the font, which can be done by putting it in a standard location or by setting +# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the +# directory containing the font. DOT_FONTNAME = FreeSans @@ -1516,17 +1644,16 @@ DOT_FONTSIZE = 10 -# By default doxygen will tell dot to use the output directory to look for the -# FreeSans.ttf font (which doxygen will put there itself). If you specify a -# different font using DOT_FONTNAME you can set the path where dot -# can find it using this tag. +# By default doxygen will tell dot to use the Helvetica font. +# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to +# set the path where dot can find it. DOT_FONTPATH = # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen # will generate a graph for each documented class showing the direct and # indirect inheritance relations. Setting this tag to YES will force the -# the CLASS_DIAGRAMS tag to NO. +# CLASS_DIAGRAMS tag to NO. CLASS_GRAPH = YES @@ -1548,6 +1675,15 @@ UML_LOOK = NO +# If the UML_LOOK tag is enabled, the fields and methods are shown inside +# the class node. If there are many fields or methods and many nodes the +# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS +# threshold limits the number of items for each type to make the size more +# managable. Set this to 0 for no limit. Note that the threshold may be +# exceeded by 50% before the limit is enforced. + +UML_LIMIT_NUM_FIELDS = 10 + # If set to YES, the inheritance and collaboration graphs will show the # relations between templates and their instances. @@ -1584,11 +1720,11 @@ CALLER_GRAPH = NO # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen -# will graphical hierarchy of all classes instead of a textual one. +# will generate a graphical hierarchy of all classes instead of a textual one. GRAPHICAL_HIERARCHY = YES -# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES # then doxygen will show the dependencies a directory has on other directories # in a graphical way. The dependency relations are determined by the #include # relations between the files in the directories. @@ -1596,11 +1732,22 @@ DIRECTORY_GRAPH = YES # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images -# generated by dot. Possible values are png, jpg, or gif -# If left blank png will be used. +# generated by dot. Possible values are svg, png, jpg, or gif. +# If left blank png will be used. If you choose svg you need to set +# HTML_FILE_EXTENSION to xhtml in order to make the SVG files +# visible in IE 9+ (other browsers do not have this requirement). DOT_IMAGE_FORMAT = png +# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to +# enable generation of interactive SVG images that allow zooming and panning. +# Note that this requires a modern browser other than Internet Explorer. +# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you +# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files +# visible. Older versions of IE do not have SVG support. + +INTERACTIVE_SVG = NO + # The tag DOT_PATH can be used to specify the path where the dot tool can be # found. If left blank, it is assumed the dot tool can be found in the path. @@ -1612,6 +1759,12 @@ DOTFILE_DIRS = +# The MSCFILE_DIRS tag can be used to specify one or more directories that +# contain msc files that are included in the documentation (see the +# \mscfile command). + +MSCFILE_DIRS = + # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of # nodes that will be shown in the graph. If the number of nodes in a graph # becomes larger than this value, doxygen will truncate the graph, which is This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. 
 [Plplot-cvs] SF.net SVN: plplot:[12476] trunk/bindings/tcl/tclAPI.c From: - 2013-08-09 16:48:35 Revision: 12476 http://sourceforge.net/p/plplot/code/12476 Author: airwin Date: 2013-08-09 16:48:32 +0000 (Fri, 09 Aug 2013) Log Message: ----------- Style. This is actually a fairly intrusive change but running the test_diff_psc target shows Tcl continues to give the same results as previous. Tested by Alan W. Irwin . Modified Paths: -------------- trunk/bindings/tcl/tclAPI.c Modified: trunk/bindings/tcl/tclAPI.c =================================================================== --- trunk/bindings/tcl/tclAPI.c 2013-08-09 16:21:45 UTC (rev 12475) +++ trunk/bindings/tcl/tclAPI.c 2013-08-09 16:48:32 UTC (rev 12476) @@ -4257,39 +4257,39 @@ static int plcolorbarCmd( ClientData PL_UNUSED( clientData ), Tcl_Interp *interp, - int argc, const char *argv[] ) + int argc, const char *argv[] ) { - PLFLT colorbar_width, colorbar_height; - PLINT opt, position; - PLFLT x, y, x_length, y_length; - PLINT bg_color, bb_color, bb_style; - PLFLT low_cap_color, high_cap_color; - PLINT cont_color; - PLFLT cont_width; - PLINT n_label_opts; - PLINT n_labels; - PLINT *label_opts; - char **labels; - PLINT n_axis_opts; - PLINT n_ticks; - PLINT n_sub_ticks; - PLINT n_axes; - char **axis_opts; - PLFLT *ticks; - PLINT *sub_ticks; - Tcl_Obj *list_vectors; - int n_vectors; - PLINT *vector_sizes; - PLFLT **vector_values; - int retcode; - int i; - int length; - Tcl_Obj *vector; + PLFLT colorbar_width, colorbar_height; + PLINT opt, position; + PLFLT x, y, x_length, y_length; + PLINT bg_color, bb_color, bb_style; + PLFLT low_cap_color, high_cap_color; + PLINT cont_color; + PLFLT cont_width; + PLINT n_label_opts; + PLINT n_labels; + PLINT *label_opts; + char **labels; + PLINT n_axis_opts; + PLINT n_ticks; + PLINT n_sub_ticks; + PLINT n_axes; + char **axis_opts; + PLFLT *ticks; + PLINT *sub_ticks; + Tcl_Obj *list_vectors; + int n_vectors; + PLINT *vector_sizes; + PLFLT **vector_values; + int retcode; + int i; + int length; + Tcl_Obj *vector; tclMatrix *vectorPtr; - double value; + double value; - Tcl_Obj *data[2]; + Tcl_Obj *data[2]; if ( argc != 20 ) { @@ -4311,7 +4311,7 @@ sscanf( argv[10], "%lg", &value ); low_cap_color = (PLFLT) value; sscanf( argv[11], "%lg", &value ); high_cap_color = (PLFLT) value; sscanf( argv[12], "%d", &cont_color ); - sscanf( argv[13], "%lg", &value ); cont_width = (PLFLT) value; + sscanf( argv[13], "%lg", &value ); cont_width = (PLFLT) value; label_opts = argv_to_ints( interp, argv[14], &n_label_opts ); labels = argv_to_chars( interp, argv[15], &n_labels ); axis_opts = argv_to_chars( interp, argv[16], &n_axis_opts ); @@ -4343,8 +4343,8 @@ } else { - vector_sizes = (int *) malloc( sizeof( int ) * (size_t) n_vectors ); - vector_values = (PLFLT **) malloc( sizeof( PLFLT * ) * (size_t) n_vectors ); + vector_sizes = (int *) malloc( sizeof ( int ) * (size_t) n_vectors ); + vector_values = (PLFLT **) malloc( sizeof ( PLFLT * ) * (size_t) n_vectors ); for ( i = 0; i < n_vectors; i++ ) { Tcl_ListObjIndex( interp, list_vectors, i, &vector ); @@ -4361,36 +4361,36 @@ } c_plcolorbar( &colorbar_width, &colorbar_height, - opt, position, x, y, - x_length, y_length, - bg_color, bb_color, bb_style, - low_cap_color, high_cap_color, - cont_color, cont_width, - n_labels, label_opts, (const char * const *)labels, - n_axes, (const char * const *)axis_opts, - ticks, sub_ticks, - vector_sizes, (const PLFLT * const *)vector_values ); + opt, position, x, y, + x_length, y_length, + bg_color, bb_color, bb_style, + low_cap_color, high_cap_color, + cont_color, cont_width, + n_labels, label_opts, (const char * const *) labels, + n_axes, (const char * const *) axis_opts, + ticks, sub_ticks, + vector_sizes, (const PLFLT * const *) vector_values ); if ( label_opts != NULL ) free( label_opts ); if ( labels != NULL ) { - free( labels[0] ) ; - free( labels ) ; + free( labels[0] ); + free( labels ); } if ( axis_opts != NULL ) { - free( axis_opts[0] ) ; - free( axis_opts ) ; + free( axis_opts[0] ); + free( axis_opts ); } if ( ticks != NULL ) - free( ticks ) ; + free( ticks ); if ( sub_ticks != NULL ) - free( sub_ticks ) ; + free( sub_ticks ); if ( vector_values != NULL ) { - free( vector_sizes ) ; - free( vector_values ) ; + free( vector_sizes ); + free( vector_values ); } Tcl_DecrRefCount( list_vectors ); This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. 
 [Plplot-cvs] SF.net SVN: plplot:[12475] trunk/drivers/wxwidgets_dc.cpp From: - 2013-08-09 16:21:54 Revision: 12475 http://sourceforge.net/p/plplot/code/12475 Author: airwin Date: 2013-08-09 16:21:45 +0000 (Fri, 09 Aug 2013) Log Message: ----------- Use correct API for DrawPolygon. Thanks to Joost Kuckartz for spotting this error, and he reports this fix solves an offset issue he had with wxwidgets plots. Modified Paths: -------------- trunk/drivers/wxwidgets_dc.cpp Modified: trunk/drivers/wxwidgets_dc.cpp =================================================================== --- trunk/drivers/wxwidgets_dc.cpp 2013-08-04 18:13:16 UTC (rev 12474) +++ trunk/drivers/wxwidgets_dc.cpp 2013-08-09 16:21:45 UTC (rev 12475) @@ -165,6 +165,8 @@ void wxPLDevDC::FillPolygon( PLStream *pls ) { wxPoint *points = new wxPoint[pls->dev_npts]; + wxCoord xoffset = 0; + wxCoord yoffset = 0; for ( int i = 0; i < pls->dev_npts; i++ ) { @@ -176,11 +178,11 @@ if ( pls->dev_eofill ) { - m_dc->DrawPolygon( pls->dev_npts, points, wxODDEVEN_RULE ); + m_dc->DrawPolygon( pls->dev_npts, points, xoffset, yoffset, wxODDEVEN_RULE ); } else { - m_dc->DrawPolygon( pls->dev_npts, points, wxWINDING_RULE ); + m_dc->DrawPolygon( pls->dev_npts, points, xoffset, yoffset, wxWINDING_RULE ); } delete[] points; } This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. 

Showing 5 results of 5