Changeset 1274 for trunk/source
- Timestamp:
- May 27, 2010, 10:36:45 AM (14 years ago)
- Location:
- trunk/source
- Files:
-
- 25 added
- 20 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/source/Doxyfile
r1199 r1274 1 # Doxyfile 1.5.7.1 1 # Doxyfile 1.6.1 2 3 # This file describes the settings to be used by the documentation system 4 # doxygen (www.doxygen.org) for a project 5 # 6 # All text after a hash (#) is considered a comment and will be ignored 7 # The format is: 8 # TAG = value [value, ...] 9 # For lists items can also be appended using: 10 # TAG += value [value, ...] 11 # Values that contain spaces should be placed between quotes (" ") 2 12 3 13 #--------------------------------------------------------------------------- 4 14 # Project related configuration options 5 15 #--------------------------------------------------------------------------- 16 17 # This tag specifies the encoding used for all characters in the config file 18 # that follow. The default is UTF-8 which is also the encoding used for all 19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the 20 # iconv built into libc) for the transcoding. See 21 # http://www.gnu.org/software/libiconv for the list of possible encodings. 22 6 23 DOXYFILE_ENCODING = UTF-8 24 25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 26 # by quotes) that should identify the project. 27 7 28 PROJECT_NAME = visualisation 29 30 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 31 # This could be handy for archiving the generated documentation or 32 # if some version control system is used. 33 8 34 PROJECT_NUMBER = 35 36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 37 # base path where the generated documentation will be put. 38 # If a relative path is entered, it will be relative to the location 39 # where doxygen was started. If left blank the current directory will be used. 40 9 41 OUTPUT_DIRECTORY = /Users/garnier/Work/Geant4-QtDriver/trunk/source/doxygen 42 43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 44 # 4096 sub-directories (in 2 levels) under the output directory of each output 45 # format and will distribute the generated files over these directories. 46 # Enabling this option can be useful when feeding doxygen a huge amount of 47 # source files, where putting all generated files in the same directory would 48 # otherwise cause performance problems for the file system. 49 10 50 CREATE_SUBDIRS = YES 51 52 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 53 # documentation generated by doxygen is written. Doxygen will use this 54 # information to generate all constant output in the proper language. 55 # The default language is English, other supported languages are: 56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 57 # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 58 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 59 # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 60 # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 61 # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 62 11 63 OUTPUT_LANGUAGE = French 64 65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 66 # include brief member descriptions after the members that are listed in 67 # the file and class documentation (similar to JavaDoc). 68 # Set to NO to disable this. 69 12 70 BRIEF_MEMBER_DESC = YES 71 72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 73 # the brief description of a member or function before the detailed description. 74 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 75 # brief descriptions will be completely suppressed. 76 13 77 REPEAT_BRIEF = YES 78 79 # This tag implements a quasi-intelligent brief description abbreviator 80 # that is used to form the text in various listings. Each string 81 # in this list, if found as the leading text of the brief description, will be 82 # stripped from the text and the result after processing the whole list, is 83 # used as the annotated text. Otherwise, the brief description is used as-is. 84 # If left blank, the following values are used ("$name" is automatically 85 # replaced with the name of the entity): "The $name class" "The $name widget" 86 # "The $name file" "is" "provides" "specifies" "contains" 87 # "represents" "a" "an" "the" 88 14 89 ABBREVIATE_BRIEF = 90 91 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 92 # Doxygen will generate a detailed section even if there is only a brief 93 # description. 94 15 95 ALWAYS_DETAILED_SEC = YES 96 97 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 98 # inherited members of a class in the documentation of that class as if those 99 # members were ordinary class members. Constructors, destructors and assignment 100 # operators of the base classes will not be shown. 101 16 102 INLINE_INHERITED_MEMB = YES 103 104 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 105 # path before files name in the file list and in the header files. If set 106 # to NO the shortest path that makes the file name unique will be used. 107 17 108 FULL_PATH_NAMES = YES 109 110 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 111 # can be used to strip a user-defined part of the path. Stripping is 112 # only done if one of the specified strings matches the left-hand part of 113 # the path. The tag can be used to show relative paths in the file list. 114 # If left blank the directory from which doxygen is run is used as the 115 # path to strip. 116 18 117 STRIP_FROM_PATH = 118 119 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 120 # the path mentioned in the documentation of a class, which tells 121 # the reader which header file to include in order to use a class. 122 # If left blank only the name of the header file containing the class 123 # definition is used. Otherwise one should specify the include paths that 124 # are normally passed to the compiler using the -I flag. 125 19 126 STRIP_FROM_INC_PATH = 127 128 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 129 # (but less readable) file names. This can be useful is your file systems 130 # doesn't support long names like on DOS, Mac, or CD-ROM. 131 20 132 SHORT_NAMES = NO 133 134 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 135 # will interpret the first line (until the first dot) of a JavaDoc-style 136 # comment as the brief description. If set to NO, the JavaDoc 137 # comments will behave just like regular Qt-style comments 138 # (thus requiring an explicit @brief command for a brief description.) 139 21 140 JAVADOC_AUTOBRIEF = NO 141 142 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 143 # interpret the first line (until the first dot) of a Qt-style 144 # comment as the brief description. If set to NO, the comments 145 # will behave just like regular Qt-style comments (thus requiring 146 # an explicit \brief command for a brief description.) 147 22 148 QT_AUTOBRIEF = YES 149 150 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 151 # treat a multi-line C++ special comment block (i.e. a block of //! or /// 152 # comments) as a brief description. This used to be the default behaviour. 153 # The new default is to treat a multi-line C++ comment block as a detailed 154 # description. Set this tag to YES if you prefer the old behaviour instead. 155 23 156 MULTILINE_CPP_IS_BRIEF = NO 157 158 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 159 # member inherits the documentation from any documented member that it 160 # re-implements. 161 24 162 INHERIT_DOCS = YES 163 164 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 165 # a new page for each member. If set to NO, the documentation of a member will 166 # be part of the file/class/namespace that contains it. 167 25 168 SEPARATE_MEMBER_PAGES = NO 169 170 # The TAB_SIZE tag can be used to set the number of spaces in a tab. 171 # Doxygen uses this value to replace tabs by spaces in code fragments. 172 26 173 TAB_SIZE = 8 174 175 # This tag can be used to specify a number of aliases that acts 176 # as commands in the documentation. An alias has the form "name=value". 177 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 178 # put the command \sideeffect (or @sideeffect) in the documentation, which 179 # will result in a user-defined paragraph with heading "Side Effects:". 180 # You can put \n's in the value part of an alias to insert newlines. 181 27 182 ALIASES = 183 184 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 185 # sources only. Doxygen will then generate output that is more tailored for C. 186 # For instance, some of the names that are used will be different. The list 187 # of all members will be omitted, etc. 188 28 189 OPTIMIZE_OUTPUT_FOR_C = NO 190 191 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 192 # sources only. Doxygen will then generate output that is more tailored for 193 # Java. For instance, namespaces will be presented as packages, qualified 194 # scopes will look different, etc. 195 29 196 OPTIMIZE_OUTPUT_JAVA = NO 197 198 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 199 # sources only. Doxygen will then generate output that is more tailored for 200 # Fortran. 201 30 202 OPTIMIZE_FOR_FORTRAN = NO 203 204 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 205 # sources. Doxygen will then generate output that is tailored for 206 # VHDL. 207 31 208 OPTIMIZE_OUTPUT_VHDL = NO 209 210 # Doxygen selects the parser to use depending on the extension of the files it parses. 211 # With this tag you can assign which parser to use for a given extension. 212 # Doxygen has a built-in mapping, but you can override or extend it using this tag. 213 # The format is ext=language, where ext is a file extension, and language is one of 214 # the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, 215 # Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat 216 # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), 217 # use: inc=Fortran f=C. Note that for custom extensions you also need to set 218 # FILE_PATTERNS otherwise the files are not read by doxygen. 219 220 EXTENSION_MAPPING = 221 222 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 223 # to include (a tag file for) the STL sources as input, then you should 224 # set this tag to YES in order to let doxygen match functions declarations and 225 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 226 # func(std::string) {}). This also make the inheritance and collaboration 227 # diagrams that involve STL classes more complete and accurate. 228 32 229 BUILTIN_STL_SUPPORT = NO 230 231 # If you use Microsoft's C++/CLI language, you should set this option to YES to 232 # enable parsing support. 233 33 234 CPP_CLI_SUPPORT = NO 235 236 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 237 # Doxygen will parse them like normal C++ but will assume all classes use public 238 # instead of private inheritance when no explicit protection keyword is present. 239 34 240 SIP_SUPPORT = NO 241 242 # For Microsoft's IDL there are propget and propput attributes to indicate getter 243 # and setter methods for a property. Setting this option to YES (the default) 244 # will make doxygen to replace the get and set methods by a property in the 245 # documentation. This will only work if the methods are indeed getting or 246 # setting a simple type. If this is not the case, or you want to show the 247 # methods anyway, you should set this option to NO. 248 35 249 IDL_PROPERTY_SUPPORT = YES 250 251 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 252 # tag is set to YES, then doxygen will reuse the documentation of the first 253 # member in the group (if any) for the other members of the group. By default 254 # all members of a group must be documented explicitly. 255 36 256 DISTRIBUTE_GROUP_DOC = NO 257 258 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of 259 # the same type (for instance a group of public functions) to be put as a 260 # subgroup of that type (e.g. under the Public Functions section). Set it to 261 # NO to prevent subgrouping. Alternatively, this can be done per class using 262 # the \nosubgrouping command. 263 37 264 SUBGROUPING = NO 265 266 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 267 # is documented as struct, union, or enum with the name of the typedef. So 268 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct 269 # with name TypeT. When disabled the typedef will appear as a member of a file, 270 # namespace, or class. And the struct will be named TypeS. This can typically 271 # be useful for C code in case the coding convention dictates that all compound 272 # types are typedef'ed and only the typedef is referenced, never the tag name. 273 38 274 TYPEDEF_HIDES_STRUCT = NO 275 276 # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 277 # determine which symbols to keep in memory and which to flush to disk. 278 # When the cache is full, less often used symbols will be written to disk. 279 # For small to medium size projects (<1000 input files) the default value is 280 # probably good enough. For larger projects a too small cache size can cause 281 # doxygen to be busy swapping symbols to and from disk most of the time 282 # causing a significant performance penality. 283 # If the system has enough physical memory increasing the cache will improve the 284 # performance by keeping more symbols in memory. Note that the value works on 285 # a logarithmic scale so increasing the size by one will rougly double the 286 # memory usage. The cache size is given by this formula: 287 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 288 # corresponding to a cache size of 2^16 = 65536 symbols 289 39 290 SYMBOL_CACHE_SIZE = 0 291 40 292 #--------------------------------------------------------------------------- 41 293 # Build related configuration options 42 294 #--------------------------------------------------------------------------- 295 296 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 297 # documentation are documented, even if no documentation was available. 298 # Private class members and static file members will be hidden unless 299 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 300 43 301 EXTRACT_ALL = YES 302 303 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 304 # will be included in the documentation. 305 44 306 EXTRACT_PRIVATE = YES 307 308 # If the EXTRACT_STATIC tag is set to YES all static members of a file 309 # will be included in the documentation. 310 45 311 EXTRACT_STATIC = YES 312 313 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 314 # defined locally in source files will be included in the documentation. 315 # If set to NO only classes defined in header files are included. 316 46 317 EXTRACT_LOCAL_CLASSES = YES 318 319 # This flag is only useful for Objective-C code. When set to YES local 320 # methods, which are defined in the implementation section but not in 321 # the interface are included in the documentation. 322 # If set to NO (the default) only methods in the interface are included. 323 47 324 EXTRACT_LOCAL_METHODS = YES 325 326 # If this flag is set to YES, the members of anonymous namespaces will be 327 # extracted and appear in the documentation as a namespace called 328 # 'anonymous_namespace{file}', where file will be replaced with the base 329 # name of the file that contains the anonymous namespace. By default 330 # anonymous namespace are hidden. 331 48 332 EXTRACT_ANON_NSPACES = NO 333 334 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 335 # undocumented members of documented classes, files or namespaces. 336 # If set to NO (the default) these members will be included in the 337 # various overviews, but no documentation section is generated. 338 # This option has no effect if EXTRACT_ALL is enabled. 339 49 340 HIDE_UNDOC_MEMBERS = NO 341 342 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 343 # undocumented classes that are normally visible in the class hierarchy. 344 # If set to NO (the default) these classes will be included in the various 345 # overviews. This option has no effect if EXTRACT_ALL is enabled. 346 50 347 HIDE_UNDOC_CLASSES = NO 348 349 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 350 # friend (class|struct|union) declarations. 351 # If set to NO (the default) these declarations will be included in the 352 # documentation. 353 51 354 HIDE_FRIEND_COMPOUNDS = NO 355 356 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 357 # documentation blocks found inside the body of a function. 358 # If set to NO (the default) these blocks will be appended to the 359 # function's detailed documentation block. 360 52 361 HIDE_IN_BODY_DOCS = NO 362 363 # The INTERNAL_DOCS tag determines if documentation 364 # that is typed after a \internal command is included. If the tag is set 365 # to NO (the default) then the documentation will be excluded. 366 # Set it to YES to include the internal documentation. 367 53 368 INTERNAL_DOCS = YES 369 370 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 371 # file names in lower-case letters. If set to YES upper-case letters are also 372 # allowed. This is useful if you have classes or files whose names only differ 373 # in case and if your file system supports case sensitive file names. Windows 374 # and Mac users are advised to set this option to NO. 375 54 376 CASE_SENSE_NAMES = NO 377 378 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 379 # will show members with their full class and namespace scopes in the 380 # documentation. If set to YES the scope will be hidden. 381 55 382 HIDE_SCOPE_NAMES = NO 383 384 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 385 # will put a list of the files that are included by a file in the documentation 386 # of that file. 387 56 388 SHOW_INCLUDE_FILES = YES 389 390 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 391 # is inserted in the documentation for inline members. 392 57 393 INLINE_INFO = YES 394 395 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 396 # will sort the (detailed) documentation of file and class members 397 # alphabetically by member name. If set to NO the members will appear in 398 # declaration order. 399 58 400 SORT_MEMBER_DOCS = YES 401 402 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 403 # brief documentation of file, namespace and class members alphabetically 404 # by member name. If set to NO (the default) the members will appear in 405 # declaration order. 406 59 407 SORT_BRIEF_DOCS = NO 408 409 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 410 # will sort the (brief and detailed) documentation of class members so that 411 # constructors and destructors are listed first. If set to NO (the default) 412 # the constructors will appear in the respective orders defined by 413 # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 414 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 415 # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 416 417 SORT_MEMBERS_CTORS_1ST = NO 418 419 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 420 # hierarchy of group names into alphabetical order. If set to NO (the default) 421 # the group names will appear in their defined order. 422 60 423 SORT_GROUP_NAMES = NO 424 425 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 426 # sorted by fully-qualified names, including namespaces. If set to 427 # NO (the default), the class list will be sorted only by class name, 428 # not including the namespace part. 429 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 430 # Note: This option applies only to the class list, not to the 431 # alphabetical list. 432 61 433 SORT_BY_SCOPE_NAME = NO 434 435 # The GENERATE_TODOLIST tag can be used to enable (YES) or 436 # disable (NO) the todo list. This list is created by putting \todo 437 # commands in the documentation. 438 62 439 GENERATE_TODOLIST = YES 440 441 # The GENERATE_TESTLIST tag can be used to enable (YES) or 442 # disable (NO) the test list. This list is created by putting \test 443 # commands in the documentation. 444 63 445 GENERATE_TESTLIST = YES 446 447 # The GENERATE_BUGLIST tag can be used to enable (YES) or 448 # disable (NO) the bug list. This list is created by putting \bug 449 # commands in the documentation. 450 64 451 GENERATE_BUGLIST = YES 452 453 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 454 # disable (NO) the deprecated list. This list is created by putting 455 # \deprecated commands in the documentation. 456 65 457 GENERATE_DEPRECATEDLIST= YES 458 459 # The ENABLED_SECTIONS tag can be used to enable conditional 460 # documentation sections, marked by \if sectionname ... \endif. 461 66 462 ENABLED_SECTIONS = 463 464 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 465 # the initial value of a variable or define consists of for it to appear in 466 # the documentation. If the initializer consists of more lines than specified 467 # here it will be hidden. Use a value of 0 to hide initializers completely. 468 # The appearance of the initializer of individual variables and defines in the 469 # documentation can be controlled using \showinitializer or \hideinitializer 470 # command in the documentation regardless of this setting. 471 67 472 MAX_INITIALIZER_LINES = 30 473 474 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 475 # at the bottom of the documentation of classes and structs. If set to YES the 476 # list will mention the files that were used to generate the documentation. 477 68 478 SHOW_USED_FILES = YES 479 480 # If the sources in your project are distributed over multiple directories 481 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 482 # in the documentation. The default is NO. 483 69 484 SHOW_DIRECTORIES = YES 485 486 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. 487 # This will remove the Files entry from the Quick Index and from the 488 # Folder Tree View (if specified). The default is YES. 489 70 490 SHOW_FILES = YES 491 492 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the 493 # Namespaces page. This will remove the Namespaces entry from the Quick Index 494 # and from the Folder Tree View (if specified). The default is YES. 495 71 496 SHOW_NAMESPACES = YES 497 498 # The FILE_VERSION_FILTER tag can be used to specify a program or script that 499 # doxygen should invoke to get the current version for each file (typically from 500 # the version control system). Doxygen will invoke the program by executing (via 501 # popen()) the command <command> <input-file>, where <command> is the value of 502 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 503 # provided by doxygen. Whatever the program writes to standard output 504 # is used as the file version. See the manual for examples. 505 72 506 FILE_VERSION_FILTER = 507 508 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by 509 # doxygen. The layout file controls the global structure of the generated output files 510 # in an output format independent way. The create the layout file that represents 511 # doxygen's defaults, run doxygen with the -l option. You can optionally specify a 512 # file name after the option, if omitted DoxygenLayout.xml will be used as the name 513 # of the layout file. 514 73 515 LAYOUT_FILE = 516 74 517 #--------------------------------------------------------------------------- 75 518 # configuration options related to warning and progress messages 76 519 #--------------------------------------------------------------------------- 520 521 # The QUIET tag can be used to turn on/off the messages that are generated 522 # by doxygen. Possible values are YES and NO. If left blank NO is used. 523 77 524 QUIET = NO 525 526 # The WARNINGS tag can be used to turn on/off the warning messages that are 527 # generated by doxygen. Possible values are YES and NO. If left blank 528 # NO is used. 529 78 530 WARNINGS = NO 531 532 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 533 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 534 # automatically be disabled. 535 79 536 WARN_IF_UNDOCUMENTED = NO 537 538 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 539 # potential errors in the documentation, such as not documenting some 540 # parameters in a documented function, or documenting parameters that 541 # don't exist or using markup commands wrongly. 542 80 543 WARN_IF_DOC_ERROR = NO 544 545 # This WARN_NO_PARAMDOC option can be abled to get warnings for 546 # functions that are documented, but have no documentation for their parameters 547 # or return value. If set to NO (the default) doxygen will only warn about 548 # wrong or incomplete parameter documentation, but not about the absence of 549 # documentation. 550 81 551 WARN_NO_PARAMDOC = NO 82 WARN_FORMAT = "$file:$line: $text " 552 553 # The WARN_FORMAT tag determines the format of the warning messages that 554 # doxygen can produce. The string should contain the $file, $line, and $text 555 # tags, which will be replaced by the file and line number from which the 556 # warning originated and the warning text. Optionally the format may contain 557 # $version, which will be replaced by the version of the file (if it could 558 # be obtained via FILE_VERSION_FILTER) 559 560 WARN_FORMAT = "$file:$line: $text" 561 562 # The WARN_LOGFILE tag can be used to specify a file to which warning 563 # and error messages should be written. If left blank the output is written 564 # to stderr. 565 83 566 WARN_LOGFILE = 567 84 568 #--------------------------------------------------------------------------- 85 569 # configuration options related to the input files 86 570 #--------------------------------------------------------------------------- 571 572 # The INPUT tag can be used to specify the files and/or directories that contain 573 # documented source files. You may enter file names like "myfile.cpp" or 574 # directories like "/usr/src/myproject". Separate the files or directories 575 # with spaces. 576 87 577 INPUT = /Users/garnier/Work/Geant4-QtDriver/trunk/source/ 578 579 # This tag can be used to specify the character encoding of the source files 580 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 581 # also the default input encoding. Doxygen uses libiconv (or the iconv built 582 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 583 # the list of possible encodings. 584 88 585 INPUT_ENCODING = UTF-8 586 587 # If the value of the INPUT tag contains directories, you can use the 588 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 589 # and *.h) to filter out the source-files in the directories. If left 590 # blank the following patterns are tested: 591 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 592 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 593 89 594 FILE_PATTERNS = *.cc \ 90 595 *.hh \ … … 92 597 *.h \ 93 598 *.icc 599 600 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 601 # should be searched for input files as well. Possible values are YES and NO. 602 # If left blank NO is used. 603 94 604 RECURSIVE = YES 95 EXCLUDE = 605 606 # The EXCLUDE tag can be used to specify files and/or directories that should 607 # excluded from the INPUT source files. This way you can easily exclude a 608 # subdirectory from a directory tree whose root is specified with the INPUT tag. 609 610 EXCLUDE = .svn \ 611 CVS 612 613 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or 614 # directories that are symbolic links (a Unix filesystem feature) are excluded 615 # from the input. 616 96 617 EXCLUDE_SYMLINKS = NO 97 EXCLUDE_PATTERNS = 618 619 # If the value of the INPUT tag contains directories, you can use the 620 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 621 # certain files from those directories. Note that the wildcards are matched 622 # against the file with absolute path, so to exclude all test directories 623 # for example use the pattern */test/* 624 625 EXCLUDE_PATTERNS = .svn 626 627 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 628 # (namespaces, classes, functions, etc.) that should be excluded from the 629 # output. The symbol name can be a fully qualified name, a word, or if the 630 # wildcard * is used, a substring. Examples: ANamespace, AClass, 631 # AClass::ANamespace, ANamespace::*Test 632 98 633 EXCLUDE_SYMBOLS = 634 635 # The EXAMPLE_PATH tag can be used to specify one or more files or 636 # directories that contain example code fragments that are included (see 637 # the \include command). 638 99 639 EXAMPLE_PATH = 640 641 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 642 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 643 # and *.h) to filter out the source-files in the directories. If left 644 # blank all files are included. 645 100 646 EXAMPLE_PATTERNS = 647 648 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 649 # searched for input files to be used with the \include or \dontinclude 650 # commands irrespective of the value of the RECURSIVE tag. 651 # Possible values are YES and NO. If left blank NO is used. 652 101 653 EXAMPLE_RECURSIVE = NO 654 655 # The IMAGE_PATH tag can be used to specify one or more files or 656 # directories that contain image that are included in the documentation (see 657 # the \image command). 658 102 659 IMAGE_PATH = 660 661 # The INPUT_FILTER tag can be used to specify a program that doxygen should 662 # invoke to filter for each input file. Doxygen will invoke the filter program 663 # by executing (via popen()) the command <filter> <input-file>, where <filter> 664 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an 665 # input file. Doxygen will then use the output that the filter program writes 666 # to standard output. If FILTER_PATTERNS is specified, this tag will be 667 # ignored. 668 103 669 INPUT_FILTER = 670 671 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 672 # basis. Doxygen will compare the file name with each pattern and apply the 673 # filter if there is a match. The filters are a list of the form: 674 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 675 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 676 # is applied to all files. 677 104 678 FILTER_PATTERNS = 679 680 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 681 # INPUT_FILTER) will be used to filter the input files when producing source 682 # files to browse (i.e. when SOURCE_BROWSER is set to YES). 683 105 684 FILTER_SOURCE_FILES = NO 685 106 686 #--------------------------------------------------------------------------- 107 687 # configuration options related to source browsing 108 688 #--------------------------------------------------------------------------- 689 690 # If the SOURCE_BROWSER tag is set to YES then a list of source files will 691 # be generated. Documented entities will be cross-referenced with these sources. 692 # Note: To get rid of all source code in the generated output, make sure also 693 # VERBATIM_HEADERS is set to NO. 694 109 695 SOURCE_BROWSER = YES 696 697 # Setting the INLINE_SOURCES tag to YES will include the body 698 # of functions and classes directly in the documentation. 699 110 700 INLINE_SOURCES = YES 701 702 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 703 # doxygen to hide any special comment blocks from generated source code 704 # fragments. Normal C and C++ comments will always remain visible. 705 111 706 STRIP_CODE_COMMENTS = YES 707 708 # If the REFERENCED_BY_RELATION tag is set to YES 709 # then for each documented function all documented 710 # functions referencing it will be listed. 711 112 712 REFERENCED_BY_RELATION = YES 713 714 # If the REFERENCES_RELATION tag is set to YES 715 # then for each documented function all documented entities 716 # called/used by that function will be listed. 717 113 718 REFERENCES_RELATION = YES 719 720 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 721 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 722 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 723 # link to the source code. Otherwise they will link to the documentation. 724 114 725 REFERENCES_LINK_SOURCE = YES 726 727 # If the USE_HTAGS tag is set to YES then the references to source code 728 # will point to the HTML generated by the htags(1) tool instead of doxygen 729 # built-in source browser. The htags tool is part of GNU's global source 730 # tagging system (see http://www.gnu.org/software/global/global.html). You 731 # will need version 4.8.6 or higher. 732 115 733 USE_HTAGS = NO 734 735 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 736 # will generate a verbatim copy of the header file for each class for 737 # which an include is specified. Set to NO to disable this. 738 116 739 VERBATIM_HEADERS = YES 740 117 741 #--------------------------------------------------------------------------- 118 742 # configuration options related to the alphabetical class index 119 743 #--------------------------------------------------------------------------- 744 745 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 746 # of all compounds will be generated. Enable this if the project 747 # contains a lot of classes, structs, unions or interfaces. 748 120 749 ALPHABETICAL_INDEX = YES 750 751 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 752 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 753 # in which this list will be split (can be a number in the range [1..20]) 754 121 755 COLS_IN_ALPHA_INDEX = 5 756 757 # In case all classes in a project start with a common prefix, all 758 # classes will be put under the same header in the alphabetical index. 759 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 760 # should be ignored while generating the index headers. 761 122 762 IGNORE_PREFIX = 763 123 764 #--------------------------------------------------------------------------- 124 765 # configuration options related to the HTML output 125 766 #--------------------------------------------------------------------------- 767 768 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 769 # generate HTML output. 770 126 771 GENERATE_HTML = YES 772 773 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 774 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 775 # put in front of it. If left blank `html' will be used as the default path. 776 127 777 HTML_OUTPUT = html 778 779 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 780 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 781 # doxygen will generate files with .html extension. 782 128 783 HTML_FILE_EXTENSION = .html 784 785 # The HTML_HEADER tag can be used to specify a personal HTML header for 786 # each generated HTML page. If it is left blank doxygen will generate a 787 # standard header. 788 129 789 HTML_HEADER = 790 791 # The HTML_FOOTER tag can be used to specify a personal HTML footer for 792 # each generated HTML page. If it is left blank doxygen will generate a 793 # standard footer. 794 130 795 HTML_FOOTER = 796 797 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 798 # style sheet that is used by each HTML page. It can be used to 799 # fine-tune the look of the HTML output. If the tag is left blank doxygen 800 # will generate a default style sheet. Note that doxygen will try to copy 801 # the style sheet file to the HTML output directory, so don't put your own 802 # stylesheet in the HTML output directory as well, or it will be erased! 803 131 804 HTML_STYLESHEET = 805 806 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 807 # files or namespaces will be aligned in HTML using tables. If set to 808 # NO a bullet list will be used. 809 132 810 HTML_ALIGN_MEMBERS = YES 811 812 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 813 # documentation will contain sections that can be hidden and shown after the 814 # page has loaded. For this to work a browser that supports 815 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 816 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 817 133 818 HTML_DYNAMIC_SECTIONS = NO 819 820 # If the GENERATE_DOCSET tag is set to YES, additional index files 821 # will be generated that can be used as input for Apple's Xcode 3 822 # integrated development environment, introduced with OSX 10.5 (Leopard). 823 # To create a documentation set, doxygen will generate a Makefile in the 824 # HTML output directory. Running make will produce the docset in that 825 # directory and running "make install" will install the docset in 826 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 827 # it at startup. 828 # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. 829 134 830 GENERATE_DOCSET = NO 831 832 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 833 # feed. A documentation feed provides an umbrella under which multiple 834 # documentation sets from a single provider (such as a company or product suite) 835 # can be grouped. 836 135 837 DOCSET_FEEDNAME = "Doxygen generated docs" 838 839 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 840 # should uniquely identify the documentation set bundle. This should be a 841 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 842 # will append .docset to the name. 843 136 844 DOCSET_BUNDLE_ID = org.doxygen.Project 845 846 # If the GENERATE_HTMLHELP tag is set to YES, additional index files 847 # will be generated that can be used as input for tools like the 848 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 849 # of the generated HTML documentation. 850 137 851 GENERATE_HTMLHELP = NO 852 853 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 854 # be used to specify the file name of the resulting .chm file. You 855 # can add a path in front of the file if the result should not be 856 # written to the html output directory. 857 138 858 CHM_FILE = 859 860 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 861 # be used to specify the location (absolute path including file name) of 862 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 863 # the HTML help compiler on the generated index.hhp. 864 139 865 HHC_LOCATION = 866 867 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 868 # controls if a separate .chi index file is generated (YES) or that 869 # it should be included in the master .chm file (NO). 870 140 871 GENERATE_CHI = NO 872 873 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 874 # is used to encode HtmlHelp index (hhk), content (hhc) and project file 875 # content. 876 141 877 CHM_INDEX_ENCODING = 878 879 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 880 # controls whether a binary table of contents is generated (YES) or a 881 # normal table of contents (NO) in the .chm file. 882 142 883 BINARY_TOC = NO 884 885 # The TOC_EXPAND flag can be set to YES to add extra items for group members 886 # to the contents of the HTML help documentation and to the tree view. 887 143 888 TOC_EXPAND = NO 889 890 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER 891 # are set, an additional index file will be generated that can be used as input for 892 # Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated 893 # HTML documentation. 894 144 895 GENERATE_QHP = NO 896 897 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can 898 # be used to specify the file name of the resulting .qch file. 899 # The path specified is relative to the HTML output folder. 900 145 901 QCH_FILE = 902 903 # The QHP_NAMESPACE tag specifies the namespace to use when generating 904 # Qt Help Project output. For more information please see 905 # http://doc.trolltech.com/qthelpproject.html#namespace 906 146 907 QHP_NAMESPACE = org.doxygen.Project 908 909 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 910 # Qt Help Project output. For more information please see 911 # http://doc.trolltech.com/qthelpproject.html#virtual-folders 912 147 913 QHP_VIRTUAL_FOLDER = doc 914 915 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. 916 # For more information please see 917 # http://doc.trolltech.com/qthelpproject.html#custom-filters 918 919 QHP_CUST_FILTER_NAME = 920 921 # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see 922 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>. 923 924 QHP_CUST_FILTER_ATTRS = 925 926 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's 927 # filter section matches. 928 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>. 929 930 QHP_SECT_FILTER_ATTRS = 931 932 # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 933 # be used to specify the location of Qt's qhelpgenerator. 934 # If non-empty doxygen will try to run qhelpgenerator on the generated 935 # .qhp file. 936 148 937 QHG_LOCATION = 938 939 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at 940 # top of each HTML page. The value NO (the default) enables the index and 941 # the value YES disables it. 942 149 943 DISABLE_INDEX = NO 944 945 # This tag can be used to set the number of enum values (range [1..20]) 946 # that doxygen will group on one line in the generated HTML documentation. 947 150 948 ENUM_VALUES_PER_LINE = 4 949 950 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 951 # structure should be generated to display hierarchical information. 952 # If the tag value is set to YES, a side panel will be generated 953 # containing a tree-like index structure (just like the one that 954 # is generated for HTML Help). For this to work a browser that supports 955 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 956 # Windows users are probably better off using the HTML help feature. 957 151 958 GENERATE_TREEVIEW = YES 959 960 # By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 961 # and Class Hierarchy pages using a tree view instead of an ordered list. 962 963 USE_INLINE_TREES = NO 964 965 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 966 # used to set the initial width (in pixels) of the frame in which the tree 967 # is shown. 968 152 969 TREEVIEW_WIDTH = 250 970 971 # Use this tag to change the font size of Latex formulas included 972 # as images in the HTML documentation. The default is 10. Note that 973 # when you change the font size after a successful doxygen run you need 974 # to manually remove any form_*.png images from the HTML output directory 975 # to force them to be regenerated. 976 153 977 FORMULA_FONTSIZE = 10 978 979 # When the SEARCHENGINE tag is enable doxygen will generate a search box 980 # for the HTML output. The underlying search engine uses javascript 981 # and DHTML and should work on any modern browser. Note that when using 982 # HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP) 983 # there is already a search function so this one should typically 984 # be disabled. 985 986 SEARCHENGINE = NO 987 154 988 #--------------------------------------------------------------------------- 155 989 # configuration options related to the LaTeX output 156 990 #--------------------------------------------------------------------------- 991 992 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 993 # generate Latex output. 994 157 995 GENERATE_LATEX = NO 996 997 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 998 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 999 # put in front of it. If left blank `latex' will be used as the default path. 1000 158 1001 LATEX_OUTPUT = latex 1002 1003 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 1004 # invoked. If left blank `latex' will be used as the default command name. 1005 159 1006 LATEX_CMD_NAME = latex 1007 1008 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 1009 # generate index for LaTeX. If left blank `makeindex' will be used as the 1010 # default command name. 1011 160 1012 MAKEINDEX_CMD_NAME = makeindex 1013 1014 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 1015 # LaTeX documents. This may be useful for small projects and may help to 1016 # save some trees in general. 1017 161 1018 COMPACT_LATEX = NO 1019 1020 # The PAPER_TYPE tag can be used to set the paper type that is used 1021 # by the printer. Possible values are: a4, a4wide, letter, legal and 1022 # executive. If left blank a4wide will be used. 1023 162 1024 PAPER_TYPE = a4wide 1025 1026 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 1027 # packages that should be included in the LaTeX output. 1028 163 1029 EXTRA_PACKAGES = 1030 1031 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 1032 # the generated latex document. The header should contain everything until 1033 # the first chapter. If it is left blank doxygen will generate a 1034 # standard header. Notice: only use this tag if you know what you are doing! 1035 164 1036 LATEX_HEADER = 1037 1038 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 1039 # is prepared for conversion to pdf (using ps2pdf). The pdf file will 1040 # contain links (just like the HTML output) instead of page references 1041 # This makes the output suitable for online browsing using a pdf viewer. 1042 165 1043 PDF_HYPERLINKS = NO 1044 1045 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 1046 # plain latex in the generated Makefile. Set this option to YES to get a 1047 # higher quality PDF documentation. 1048 166 1049 USE_PDFLATEX = NO 1050 1051 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 1052 # command to the generated LaTeX files. This will instruct LaTeX to keep 1053 # running if errors occur, instead of asking the user for help. 1054 # This option is also used when generating formulas in HTML. 1055 167 1056 LATEX_BATCHMODE = NO 1057 1058 # If LATEX_HIDE_INDICES is set to YES then doxygen will not 1059 # include the index chapters (such as File Index, Compound Index, etc.) 1060 # in the output. 1061 168 1062 LATEX_HIDE_INDICES = NO 1063 1064 # If LATEX_SOURCE_CODE is set to YES then doxygen will include 1065 # source code with syntax highlighting in the LaTeX output. 1066 # Note that which sources are shown also depends on other settings 1067 # such as SOURCE_BROWSER. 1068 1069 LATEX_SOURCE_CODE = NO 1070 169 1071 #--------------------------------------------------------------------------- 170 1072 # configuration options related to the RTF output 171 1073 #--------------------------------------------------------------------------- 1074 1075 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 1076 # The RTF output is optimized for Word 97 and may not look very pretty with 1077 # other RTF readers or editors. 1078 172 1079 GENERATE_RTF = NO 1080 1081 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 1082 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1083 # put in front of it. If left blank `rtf' will be used as the default path. 1084 173 1085 RTF_OUTPUT = rtf 1086 1087 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 1088 # RTF documents. This may be useful for small projects and may help to 1089 # save some trees in general. 1090 174 1091 COMPACT_RTF = NO 1092 1093 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 1094 # will contain hyperlink fields. The RTF file will 1095 # contain links (just like the HTML output) instead of page references. 1096 # This makes the output suitable for online browsing using WORD or other 1097 # programs which support those fields. 1098 # Note: wordpad (write) and others do not support links. 1099 175 1100 RTF_HYPERLINKS = NO 1101 1102 # Load stylesheet definitions from file. Syntax is similar to doxygen's 1103 # config file, i.e. a series of assignments. You only have to provide 1104 # replacements, missing definitions are set to their default value. 1105 176 1106 RTF_STYLESHEET_FILE = 1107 1108 # Set optional variables used in the generation of an rtf document. 1109 # Syntax is similar to doxygen's config file. 1110 177 1111 RTF_EXTENSIONS_FILE = 1112 178 1113 #--------------------------------------------------------------------------- 179 1114 # configuration options related to the man page output 180 1115 #--------------------------------------------------------------------------- 1116 1117 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 1118 # generate man pages 1119 181 1120 GENERATE_MAN = NO 1121 1122 # The MAN_OUTPUT tag is used to specify where the man pages will be put. 1123 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1124 # put in front of it. If left blank `man' will be used as the default path. 1125 182 1126 MAN_OUTPUT = man 1127 1128 # The MAN_EXTENSION tag determines the extension that is added to 1129 # the generated man pages (default is the subroutine's section .3) 1130 183 1131 MAN_EXTENSION = .3 1132 1133 # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 1134 # then it will generate one additional man file for each entity 1135 # documented in the real man page(s). These additional files 1136 # only source the real man page, but without them the man command 1137 # would be unable to find the correct page. The default is NO. 1138 184 1139 MAN_LINKS = NO 1140 185 1141 #--------------------------------------------------------------------------- 186 1142 # configuration options related to the XML output 187 1143 #--------------------------------------------------------------------------- 1144 1145 # If the GENERATE_XML tag is set to YES Doxygen will 1146 # generate an XML file that captures the structure of 1147 # the code including all documentation. 1148 188 1149 GENERATE_XML = NO 1150 1151 # The XML_OUTPUT tag is used to specify where the XML pages will be put. 1152 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1153 # put in front of it. If left blank `xml' will be used as the default path. 1154 189 1155 XML_OUTPUT = xml 1156 1157 # The XML_SCHEMA tag can be used to specify an XML schema, 1158 # which can be used by a validating XML parser to check the 1159 # syntax of the XML files. 1160 190 1161 XML_SCHEMA = 1162 1163 # The XML_DTD tag can be used to specify an XML DTD, 1164 # which can be used by a validating XML parser to check the 1165 # syntax of the XML files. 1166 191 1167 XML_DTD = 1168 1169 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will 1170 # dump the program listings (including syntax highlighting 1171 # and cross-referencing information) to the XML output. Note that 1172 # enabling this will significantly increase the size of the XML output. 1173 192 1174 XML_PROGRAMLISTING = YES 1175 193 1176 #--------------------------------------------------------------------------- 194 1177 # configuration options for the AutoGen Definitions output 195 1178 #--------------------------------------------------------------------------- 1179 1180 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 1181 # generate an AutoGen Definitions (see autogen.sf.net) file 1182 # that captures the structure of the code including all 1183 # documentation. Note that this feature is still experimental 1184 # and incomplete at the moment. 1185 196 1186 GENERATE_AUTOGEN_DEF = NO 1187 197 1188 #--------------------------------------------------------------------------- 198 1189 # configuration options related to the Perl module output 199 1190 #--------------------------------------------------------------------------- 1191 1192 # If the GENERATE_PERLMOD tag is set to YES Doxygen will 1193 # generate a Perl module file that captures the structure of 1194 # the code including all documentation. Note that this 1195 # feature is still experimental and incomplete at the 1196 # moment. 1197 200 1198 GENERATE_PERLMOD = NO 1199 1200 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 1201 # the necessary Makefile rules, Perl scripts and LaTeX code to be able 1202 # to generate PDF and DVI output from the Perl module output. 1203 201 1204 PERLMOD_LATEX = NO 1205 1206 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 1207 # nicely formatted so it can be parsed by a human reader. This is useful 1208 # if you want to understand what is going on. On the other hand, if this 1209 # tag is set to NO the size of the Perl module output will be much smaller 1210 # and Perl will parse it just the same. 1211 202 1212 PERLMOD_PRETTY = YES 1213 1214 # The names of the make variables in the generated doxyrules.make file 1215 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 1216 # This is useful so different doxyrules.make files included by the same 1217 # Makefile don't overwrite each other's variables. 1218 203 1219 PERLMOD_MAKEVAR_PREFIX = 204 #--------------------------------------------------------------------------- 205 # Configuration options related to the preprocessor 206 #--------------------------------------------------------------------------- 1220 1221 #--------------------------------------------------------------------------- 1222 # Configuration options related to the preprocessor 1223 #--------------------------------------------------------------------------- 1224 1225 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 1226 # evaluate all C-preprocessor directives found in the sources and include 1227 # files. 1228 207 1229 ENABLE_PREPROCESSING = NO 1230 1231 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 1232 # names in the source code. If set to NO (the default) only conditional 1233 # compilation will be performed. Macro expansion can be done in a controlled 1234 # way by setting EXPAND_ONLY_PREDEF to YES. 1235 208 1236 MACRO_EXPANSION = NO 1237 1238 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 1239 # then the macro expansion is limited to the macros specified with the 1240 # PREDEFINED and EXPAND_AS_DEFINED tags. 1241 209 1242 EXPAND_ONLY_PREDEF = NO 1243 1244 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 1245 # in the INCLUDE_PATH (see below) will be search if a #include is found. 1246 210 1247 SEARCH_INCLUDES = YES 1248 1249 # The INCLUDE_PATH tag can be used to specify one or more directories that 1250 # contain include files that are not input files but should be processed by 1251 # the preprocessor. 1252 211 1253 INCLUDE_PATH = 1254 1255 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 1256 # patterns (like *.h and *.hpp) to filter out the header-files in the 1257 # directories. If left blank, the patterns specified with FILE_PATTERNS will 1258 # be used. 1259 212 1260 INCLUDE_FILE_PATTERNS = 1261 1262 # The PREDEFINED tag can be used to specify one or more macro names that 1263 # are defined before the preprocessor is started (similar to the -D option of 1264 # gcc). The argument of the tag is a list of macros of the form: name 1265 # or name=definition (no spaces). If the definition and the = are 1266 # omitted =1 is assumed. To prevent a macro definition from being 1267 # undefined via #undef or recursively expanded use the := operator 1268 # instead of the = operator. 1269 213 1270 PREDEFINED = 1271 1272 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 1273 # this tag can be used to specify a list of macro names that should be expanded. 1274 # The macro definition that is found in the sources will be used. 1275 # Use the PREDEFINED tag if you want to use a different macro definition. 1276 214 1277 EXPAND_AS_DEFINED = 1278 1279 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 1280 # doxygen's preprocessor will remove all function-like macros that are alone 1281 # on a line, have an all uppercase name, and do not end with a semicolon. Such 1282 # function macros are typically used for boiler-plate code, and will confuse 1283 # the parser if not removed. 1284 215 1285 SKIP_FUNCTION_MACROS = YES 216 #--------------------------------------------------------------------------- 217 # Configuration::additions related to external references 218 #--------------------------------------------------------------------------- 1286 1287 #--------------------------------------------------------------------------- 1288 # Configuration::additions related to external references 1289 #--------------------------------------------------------------------------- 1290 1291 # The TAGFILES option can be used to specify one or more tagfiles. 1292 # Optionally an initial location of the external documentation 1293 # can be added for each tagfile. The format of a tag file without 1294 # this location is as follows: 1295 # TAGFILES = file1 file2 ... 1296 # Adding location for the tag files is done as follows: 1297 # TAGFILES = file1=loc1 "file2 = loc2" ... 1298 # where "loc1" and "loc2" can be relative or absolute paths or 1299 # URLs. If a location is present for each tag, the installdox tool 1300 # does not have to be run to correct the links. 1301 # Note that each tag file must have a unique name 1302 # (where the name does NOT include the path) 1303 # If a tag file is not located in the directory in which doxygen 1304 # is run, you must also specify the path to the tagfile here. 1305 219 1306 TAGFILES = 1307 1308 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 1309 # a tag file that is based on the input files it reads. 1310 220 1311 GENERATE_TAGFILE = 1312 1313 # If the ALLEXTERNALS tag is set to YES all external classes will be listed 1314 # in the class index. If set to NO only the inherited external classes 1315 # will be listed. 1316 221 1317 ALLEXTERNALS = NO 1318 1319 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 1320 # in the modules index. If set to NO, only the current project's groups will 1321 # be listed. 1322 222 1323 EXTERNAL_GROUPS = YES 1324 1325 # The PERL_PATH should be the absolute path and name of the perl script 1326 # interpreter (i.e. the result of `which perl'). 1327 223 1328 PERL_PATH = /usr/bin/perl 224 #--------------------------------------------------------------------------- 225 # Configuration options related to the dot tool 226 #--------------------------------------------------------------------------- 1329 1330 #--------------------------------------------------------------------------- 1331 # Configuration options related to the dot tool 1332 #--------------------------------------------------------------------------- 1333 1334 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 1335 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 1336 # or super classes. Setting the tag to NO turns the diagrams off. Note that 1337 # this option is superseded by the HAVE_DOT option below. This is only a 1338 # fallback. It is recommended to install and use dot, since it yields more 1339 # powerful graphs. 1340 227 1341 CLASS_DIAGRAMS = YES 1342 1343 # You can define message sequence charts within doxygen comments using the \msc 1344 # command. Doxygen will then run the mscgen tool (see 1345 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 1346 # documentation. The MSCGEN_PATH tag allows you to specify the directory where 1347 # the mscgen tool resides. If left empty the tool is assumed to be found in the 1348 # default search path. 1349 228 1350 MSCGEN_PATH = /Applications/_Local/Doxygen.app/Contents/Resources/ 1351 1352 # If set to YES, the inheritance and collaboration graphs will hide 1353 # inheritance and usage relations if the target is undocumented 1354 # or is not a class. 1355 229 1356 HIDE_UNDOC_RELATIONS = YES 1357 1358 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 1359 # available from the path. This tool is part of Graphviz, a graph visualization 1360 # toolkit from AT&T and Lucent Bell Labs. The other options in this section 1361 # have no effect if this option is set to NO (the default) 1362 230 1363 HAVE_DOT = YES 1364 1365 # By default doxygen will write a font called FreeSans.ttf to the output 1366 # directory and reference it in all dot files that doxygen generates. This 1367 # font does not include all possible unicode characters however, so when you need 1368 # these (or just want a differently looking font) you can specify the font name 1369 # using DOT_FONTNAME. You need need to make sure dot is able to find the font, 1370 # which can be done by putting it in a standard location or by setting the 1371 # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory 1372 # containing the font. 1373 231 1374 DOT_FONTNAME = FreeSans 1375 1376 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 1377 # The default size is 10pt. 1378 232 1379 DOT_FONTSIZE = 10 1380 1381 # By default doxygen will tell dot to use the output directory to look for the 1382 # FreeSans.ttf font (which doxygen will put there itself). If you specify a 1383 # different font using DOT_FONTNAME you can set the path where dot 1384 # can find it using this tag. 1385 233 1386 DOT_FONTPATH = 1387 1388 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 1389 # will generate a graph for each documented class showing the direct and 1390 # indirect inheritance relations. Setting this tag to YES will force the 1391 # the CLASS_DIAGRAMS tag to NO. 1392 234 1393 CLASS_GRAPH = YES 1394 1395 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 1396 # will generate a graph for each documented class showing the direct and 1397 # indirect implementation dependencies (inheritance, containment, and 1398 # class references variables) of the class with other documented classes. 1399 235 1400 COLLABORATION_GRAPH = YES 1401 1402 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 1403 # will generate a graph for groups, showing the direct groups dependencies 1404 236 1405 GROUP_GRAPHS = YES 1406 1407 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 1408 # collaboration diagrams in a style similar to the OMG's Unified Modeling 1409 # Language. 1410 237 1411 UML_LOOK = YES 1412 1413 # If set to YES, the inheritance and collaboration graphs will show the 1414 # relations between templates and their instances. 1415 238 1416 TEMPLATE_RELATIONS = YES 1417 1418 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 1419 # tags are set to YES then doxygen will generate a graph for each documented 1420 # file showing the direct and indirect include dependencies of the file with 1421 # other documented files. 1422 239 1423 INCLUDE_GRAPH = YES 1424 1425 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 1426 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 1427 # documented header file showing the documented files that directly or 1428 # indirectly include this file. 1429 240 1430 INCLUDED_BY_GRAPH = YES 1431 1432 # If the CALL_GRAPH and HAVE_DOT options are set to YES then 1433 # doxygen will generate a call dependency graph for every global function 1434 # or class method. Note that enabling this option will significantly increase 1435 # the time of a run. So in most cases it will be better to enable call graphs 1436 # for selected functions only using the \callgraph command. 1437 241 1438 CALL_GRAPH = YES 1439 1440 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 1441 # doxygen will generate a caller dependency graph for every global function 1442 # or class method. Note that enabling this option will significantly increase 1443 # the time of a run. So in most cases it will be better to enable caller 1444 # graphs for selected functions only using the \callergraph command. 1445 242 1446 CALLER_GRAPH = YES 1447 1448 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 1449 # will graphical hierarchy of all classes instead of a textual one. 1450 243 1451 GRAPHICAL_HIERARCHY = YES 1452 1453 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 1454 # then doxygen will show the dependencies a directory has on other directories 1455 # in a graphical way. The dependency relations are determined by the #include 1456 # relations between the files in the directories. 1457 244 1458 DIRECTORY_GRAPH = YES 1459 1460 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 1461 # generated by dot. Possible values are png, jpg, or gif 1462 # If left blank png will be used. 1463 245 1464 DOT_IMAGE_FORMAT = png 1465 1466 # The tag DOT_PATH can be used to specify the path where the dot tool can be 1467 # found. If left blank, it is assumed the dot tool can be found in the path. 1468 246 1469 DOT_PATH = /sw/bin/ 1470 1471 # The DOTFILE_DIRS tag can be used to specify one or more directories that 1472 # contain dot files that are included in the documentation (see the 1473 # \dotfile command). 1474 247 1475 DOTFILE_DIRS = 1476 1477 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 1478 # nodes that will be shown in the graph. If the number of nodes in a graph 1479 # becomes larger than this value, doxygen will truncate the graph, which is 1480 # visualized by representing a node as a red box. Note that doxygen if the 1481 # number of direct children of the root node in a graph is already larger than 1482 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 1483 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 1484 248 1485 DOT_GRAPH_MAX_NODES = 50 1486 1487 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 1488 # graphs generated by dot. A depth value of 3 means that only nodes reachable 1489 # from the root by following a path via at most 3 edges will be shown. Nodes 1490 # that lay further from the root node will be omitted. Note that setting this 1491 # option to 1 or 2 may greatly reduce the computation time needed for large 1492 # code bases. Also note that the size of a graph can be further restricted by 1493 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 1494 249 1495 MAX_DOT_GRAPH_DEPTH = 0 1496 1497 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 1498 # background. This is disabled by default, because dot on Windows does not 1499 # seem to support this out of the box. Warning: Depending on the platform used, 1500 # enabling this option may lead to badly anti-aliased labels on the edges of 1501 # a graph (i.e. they become hard to read). 1502 250 1503 DOT_TRANSPARENT = NO 1504 1505 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 1506 # files in one run (i.e. multiple -o and -T options on the command line). This 1507 # makes dot run faster, but since only newer versions of dot (>1.8.10) 1508 # support this, this feature is disabled by default. 1509 251 1510 DOT_MULTI_TARGETS = NO 1511 1512 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 1513 # generate a legend page explaining the meaning of the various boxes and 1514 # arrows in the dot generated graphs. 1515 252 1516 GENERATE_LEGEND = YES 1517 1518 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 1519 # remove the intermediate dot files that are used to generate 1520 # the various graphs. 1521 253 1522 DOT_CLEANUP = YES 254 #---------------------------------------------------------------------------255 # Configuration::additions related to the search engine256 #---------------------------------------------------------------------------257 SEARCHENGINE = NO -
trunk/source/interfaces/History
r1261 r1274 1 $Id: History,v 1.13 3 2010/05/20 07:01:03lgarnier Exp $1 $Id: History,v 1.135 2010/05/26 14:27:14 lgarnier Exp $ 2 2 ------------------------------------------------------------------- 3 3 … … 21 21 - G4UIQt: Fix some compil errors with qt3 22 22 23 20 May, L. Garnier 23 20 May, L. Garnier (interfaces-V09-03-02) 24 24 Co-working tag : intercoms-V09-03-01 25 25 - G4UIQt: Add some changes in order to register UI in order to access -
trunk/source/interfaces/basic/src/G4UIQt.cc
r1272 r1274 25 25 // 26 26 // 27 // $Id: G4UIQt.cc,v 1.3 7 2010/05/20 07:01:03lgarnier Exp $27 // $Id: G4UIQt.cc,v 1.38 2010/05/26 14:27:14 lgarnier Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // -
trunk/source/visualization/History
r1228 r1274 1 $Id: History,v 1.46 0 2009/11/23 05:56:37 perlExp $1 $Id: History,v 1.464 2010/05/20 07:58:13 allison Exp $ 2 2 ------------------------------------------------------------------- 3 3 … … 24 24 History file for visualization category 25 25 --------------------------------------- 26 27 20th May 2010 John Allison (vis-V09-03-01) 28 - Co-working tags: intercoms-V09-03-01, interfaces-V09-03-02 29 - opengl-V09-03-01: 30 o GNUMakefile, G4OpenGLQtViewer : Better inclusion of new tabs in UI part 31 - visman-V09-03-01: 32 o Restore previous viewer after /vis/drawTree. 33 34 11th May 2010 John Allison (vis-V09-03-00) 35 - visman-09-03-00: Print i_mode warnings. 36 - modeling-V09-03-00: 37 o Replace polyhedra with solids for sections and cutaways. 38 o Trap use of i_mode and print warning. 39 - opengl-V09-03-00: 40 o Many improvements to OpenGL Qt. 41 o Speed improvements for polymarkers (e.g., trajectories). 42 o Use generic section and cutaway algorithm. 43 - gMocren-V09-03-01: printing improvement. 44 - vistest-V09-03-00: Added printEPS to test19.g4m, as suggested by Laurent. 26 45 27 46 22nd November 2009 Joseph Perl (vis-V09-02-12) -
trunk/source/visualization/OpenGL/GNUmakefile
r1254 r1274 11 11 12 12 # For debug mode 13 #CPPFLAGS += -DG4DEBUG_VIS_OGL13 CPPFLAGS += -DG4DEBUG_VIS_OGL 14 14 15 15 GLOBLIBS = libG4vis_management.lib libG4modeling.lib libG4gl2ps.lib -
trunk/source/visualization/OpenGL/History
r1254 r1274 1 $Id: History,v 1.1 69 2010/05/20 07:09:33lgarnier Exp $1 $Id: History,v 1.171 2010/05/26 14:50:56 lgarnier Exp $ 2 2 ------------------------------------------------------------------- 3 3 … … 17 17 * Reverse chronological order (last date on top), please * 18 18 ---------------------------------------------------------- 19 20th May 2010 Laurent Garnier 19 20 26th May 2010 Laurent Garnier 21 - G4OpenGLQtViewer : Some improvments with auto rotation mode. 22 23 20th May 2010 Laurent Garnier (opengl-V09-03-01) 20 24 Co-working tag : intercoms-V09-03-01, interfaces-V09-03-02 21 25 - GNUMakefile, G4OpenGLQtViewer : Better inclusion of new tabs in UI part -
trunk/source/visualization/OpenGL/include/G4OpenGLQtViewer.hh
r1260 r1274 25 25 // 26 26 // 27 // $Id: G4OpenGLQtViewer.hh,v 1.2 1 2010/01/06 15:05:29lgarnier Exp $27 // $Id: G4OpenGLQtViewer.hh,v 1.22 2010/05/26 14:50:56 lgarnier Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // -
trunk/source/visualization/OpenGL/include/G4OpenGLSceneHandler.hh
r1253 r1274 25 25 // 26 26 // 27 // $Id: G4OpenGLSceneHandler.hh,v 1.2 8 2010/04/30 13:18:32 lgarnierExp $27 // $Id: G4OpenGLSceneHandler.hh,v 1.29 2010/05/11 10:17:32 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 93 93 virtual ~G4OpenGLSceneHandler (); 94 94 95 const G4Polyhedron* CreateSectionPolyhedron();96 const G4Polyhedron* CreateCutawayPolyhedron();95 G4VSolid* CreateSectionSolid (); 96 G4VSolid* CreateCutawaySolid (); 97 97 98 98 void ClearAndDestroyAtts(); // Destroys att holders and clears pick map. -
trunk/source/visualization/OpenGL/src/G4OpenGLQtViewer.cc
r1259 r1274 25 25 // 26 26 // 27 // $Id: G4OpenGLQtViewer.cc,v 1.5 0 2010/05/20 08:13:37 allisonExp $27 // $Id: G4OpenGLQtViewer.cc,v 1.51 2010/05/26 14:50:56 lgarnier Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // -
trunk/source/visualization/OpenGL/src/G4OpenGLSceneHandler.cc
r1253 r1274 25 25 // 26 26 // 27 // $Id: G4OpenGLSceneHandler.cc,v 1.5 7 2010/04/30 13:18:32 lgarnierExp $27 // $Id: G4OpenGLSceneHandler.cc,v 1.58 2010/05/11 10:17:32 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 138 138 } 139 139 140 const G4Polyhedron* G4OpenGLSceneHandler::CreateSectionPolyhedron()140 G4VSolid* G4OpenGLSceneHandler::CreateSectionSolid () 141 141 { 142 142 // Clipping done in G4OpenGLViewer::SetView. 143 return 0;143 // return 0; 144 144 145 145 // But...OpenGL no longer seems to reconstruct clipped edges, so, 146 146 // when the BooleanProcessor is up to it, abandon this and use 147 // generic clipping in G4VSceneHandler::CreateSection Polyhedron...148 // return G4VSceneHandler::CreateSectionPolyhedron();149 } 150 151 const G4Polyhedron* G4OpenGLSceneHandler::CreateCutawayPolyhedron()147 // generic clipping in G4VSceneHandler::CreateSectionSolid... 148 return G4VSceneHandler::CreateSectionSolid(); 149 } 150 151 G4VSolid* G4OpenGLSceneHandler::CreateCutawaySolid () 152 152 { 153 153 // Cutaway done in G4OpenGLViewer::SetView. 154 return 0;154 // return 0; 155 155 156 156 // But...if not, when the BooleanProcessor is up to it... 157 // return G4VSceneHandler::CreateCutawayPolyhedron();157 return G4VSceneHandler::CreateCutawaySolid(); 158 158 } 159 159 -
trunk/source/visualization/OpenGL/src/G4OpenGLViewer.cc
r1245 r1274 25 25 // 26 26 // 27 // $Id: G4OpenGLViewer.cc,v 1.6 1 2010/04/27 15:59:10 lgarnierExp $27 // $Id: G4OpenGLViewer.cc,v 1.62 2010/05/11 10:22:37 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 271 271 // force kernel visit on change of clipping plane in 272 272 // G4OpenGLStoredViewer::CompareForKernelVisit. 273 if (fVP.IsSection () ) { // pair of back to back clip planes. 273 //if (fVP.IsSection () ) { // pair of back to back clip planes. 274 if (false) { // pair of back to back clip planes. 274 275 const G4Plane3D& s = fVP.GetSectionPlane (); 275 276 double sArray[4]; … … 293 294 const G4Planes& cutaways = fVP.GetCutawayPlanes(); 294 295 size_t nPlanes = cutaways.size(); 295 if (fVP.IsCutaway() && 296 //if (fVP.IsCutaway() && 297 if (false && 296 298 fVP.GetCutawayMode() == G4ViewParameters::cutawayIntersection && 297 299 nPlanes > 0) { … … 384 386 GLint hits = glRenderMode(GL_RENDER); 385 387 if (hits < 0) 386 G4cout << "Too many hits. Zoom in to reduce overlaps." << G4 cout;388 G4cout << "Too many hits. Zoom in to reduce overlaps." << G4endl; 387 389 else if (hits > 0) { 388 390 //G4cout << hits << " hit(s)" << G4endl; … … 390 392 for (GLint i = 0; i < hits; ++i) { 391 393 GLuint nnames = *p++; 392 *p++; //OR GLuint zmin = *p++;393 *p++; //OR GLuint zmax = *p++;394 p++; //OR GLuint zmin = *p++; 395 p++; //OR GLuint zmax = *p++; 394 396 //G4cout << "Hit " << i << ": " << nnames << " names" 395 397 // << "\nzmin: " << zmin << ", zmax: " << zmax << G4endl; … … 478 480 // Change the LC_NUMERIC value in order to have "." separtor and not "," 479 481 // This case is only useful for French, Canadien... 480 char *oldLocale = strdup(setlocale(LC_NUMERIC,NULL)); 482 char* oldLocale = (char*)(malloc(strlen(setlocale(LC_NUMERIC,NULL))+1)); 483 if(oldLocale!=NULL) strcpy(oldLocale,setlocale(LC_NUMERIC,NULL)); 481 484 setlocale(LC_NUMERIC,"C"); 482 485 -
trunk/source/visualization/gMocren/History
r1228 r1274 1 $Id: History,v 1. 9 2009/12/03 11:44:42 akimuraExp $1 $Id: History,v 1.11 2010/05/11 10:44:35 allison Exp $ 2 2 ------------------------------------------------------------------- 3 3 … … 20 20 History file for visualization/gMocren sub-category 21 21 --------------------------------------------------- 22 23 11 May 2010 John Allison (gMocren-V09-03-01) 24 - G4GMocrenFileSceneHandler.cc: Added G4cout << G4endl; to improve printing. 25 26 22 January 2010 Gabriele Cosmo (gMocren-V09-03-00) 27 Fix in G4GMocrenFileSceneHandler.cc to allow for porting on C++0x Standard: 28 made explicit with static_cast conversions from double to float. Also use 29 G4 types in consistent way. 22 30 23 31 3 December 2009 Akinori Kimura -
trunk/source/visualization/gMocren/src/G4GMocrenFileSceneHandler.cc
r1228 r1274 25 25 // 26 26 // 27 // $Id: G4GMocrenFileSceneHandler.cc,v 1.1 2 2009/12/03 11:44:42 akimuraExp $27 // $Id: G4GMocrenFileSceneHandler.cc,v 1.14 2010/05/11 10:44:11 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 93 93 94 94 //-- for a debugging 95 const bool GFDEBUG = false;96 const bool GFDEBUG_TRK = false;//true;97 const bool GFDEBUG_HIT = false;//true;95 const G4bool GFDEBUG = false; 96 const G4bool GFDEBUG_TRK = false;//true; 97 const G4bool GFDEBUG_HIT = false;//true; 98 98 const G4int GFDEBUG_DET = 0; // 0: false 99 99 … … 170 170 kbSetModalityVoxelSize = false; 171 171 172 for( int i = 0; i < 3; i++) {172 for(G4int i = 0; i < 3; i++) { 173 173 kModalitySize[i] = 0; 174 174 kNestedVolumeDimension[i] = 0; … … 182 182 { 183 183 // g4_00.gdd, g4_01.gdd, ..., g4_MAX_FILE_INDEX.gdd 184 const int MAX_FILE_INDEX = kMaxFileNum - 1 ;184 const G4int MAX_FILE_INDEX = kMaxFileNum - 1 ; 185 185 186 186 // dest directory (null if no environmental variables is set) … … 191 191 192 192 // Automatic updation of file names 193 static int currentNumber = 0;194 for( int i = currentNumber ; i < kMaxFileNum ; i++) {193 static G4int currentNumber = 0; 194 for( G4int i = currentNumber ; i < kMaxFileNum ; i++) { 195 195 196 196 // Message in the final execution … … 268 268 minmax[1] = ctdens.GetMaxCT(); 269 269 kgMocrenIO->setModalityImageMinMax(minmax); 270 std::vector< float> map;271 float dens;272 for( int i = minmax[0]; i <= minmax[1]; i++) {270 std::vector<G4float> map; 271 G4float dens; 272 for(G4int i = minmax[0]; i <= minmax[1]; i++) { 273 273 dens = ctdens.GetDensity(i); 274 274 map.push_back(dens); … … 283 283 ifile >> minmax[0] >> minmax[1]; 284 284 kgMocrenIO->setModalityImageMinMax(minmax); 285 std::vector< float> map;286 float dens;287 for( int i = minmax[0]; i <= minmax[1]; i++) {285 std::vector<G4float> map; 286 G4float dens; 287 for(G4int i = minmax[0]; i <= minmax[1]; i++) { 288 288 ifile >> dens; 289 289 map.push_back(dens); … … 329 329 kFlagSaving_g4_gdd = false; 330 330 331 std::map<Index3D, float>::iterator itr = kNestedModality.begin();331 std::map<Index3D, G4float>::iterator itr = kNestedModality.begin(); 332 332 G4int xmax=0, ymax=0, zmax=0; 333 333 for(; itr != kNestedModality.end(); itr++) { … … 347 347 348 348 G4int nxy = kModalitySize[0]*kModalitySize[1]; 349 //std::map<G4int, float>::iterator itr;350 for( int z = 0; z < kModalitySize[2]; z++) {349 //std::map<G4int, G4float>::iterator itr; 350 for(G4int z = 0; z < kModalitySize[2]; z++) { 351 351 short * modality = new short[nxy]; 352 for( int y = 0; y < kModalitySize[1]; y++) {353 for( int x = 0; x < kModalitySize[0]; x++) {354 //for( int x = kModalitySize[0]-1; x >= 0 ; x--) {352 for(G4int y = 0; y < kModalitySize[1]; y++) { 353 for(G4int x = 0; x < kModalitySize[0]; x++) { 354 //for(G4int x = kModalitySize[0]-1; x >= 0 ; x--) { 355 355 //G4int ixy = x + (kModalitySize[1]-y-1)*kModalitySize[0]; 356 356 … … 377 377 std::map<G4String, std::map<Index3D, G4double> >::iterator hitsListItr = kNestedHitsList.begin(); 378 378 379 for( int n = 0; hitsListItr != kNestedHitsList.end(); hitsListItr++, n++) {379 for(G4int n = 0; hitsListItr != kNestedHitsList.end(); hitsListItr++, n++) { 380 380 381 381 kgMocrenIO->newDoseDist(); … … 384 384 385 385 G4double minmax[2] = {DBL_MAX, -DBL_MAX}; 386 for( int z = 0 ; z < kModalitySize[2]; z++) {386 for(G4int z = 0 ; z < kModalitySize[2]; z++) { 387 387 G4double * values = new G4double[nxy]; 388 for( int y = 0; y < kModalitySize[1]; y++) {389 for( int x = 0; x < kModalitySize[0]; x++) {388 for(G4int y = 0; y < kModalitySize[1]; y++) { 389 for(G4int x = 0; x < kModalitySize[0]; x++) { 390 390 391 391 G4int ixy = x + y*kModalitySize[0]; … … 421 421 rot = kVolumeTrans3D.getRotation().inverse(); 422 422 // x 423 std::vector< float *> tracks;423 std::vector<G4float *> tracks; 424 424 unsigned char colors[3]; 425 float * trk = newfloat[6];425 G4float * trk = new G4float[6]; 426 426 tracks.push_back(trk); 427 427 … … 435 435 za -= trans; 436 436 za.transform(rot); 437 for( int i = 0; i < 3; i++) trk[i] = orig[i];438 for( int i = 0; i < 3; i++) trk[i+3] = xa[i];437 for(G4int i = 0; i < 3; i++) trk[i] = orig[i]; 438 for(G4int i = 0; i < 3; i++) trk[i+3] = xa[i]; 439 439 colors[0] = 255; colors[1] = 0; colors[2] = 0; 440 440 kgMocrenIO->addTrack(tracks, colors); 441 441 // y 442 for( int i = 0; i < 3; i++) trk[i+3] = ya[i];442 for(G4int i = 0; i < 3; i++) trk[i+3] = ya[i]; 443 443 colors[0] = 0; colors[1] = 255; colors[2] = 0; 444 444 kgMocrenIO->addTrack(tracks, colors); 445 445 // z 446 for( int i = 0; i < 3; i++) trk[i+3] = za[i];446 for(G4int i = 0; i < 3; i++) trk[i+3] = za[i]; 447 447 colors[0] = 0; colors[1] = 0; colors[2] = 255; 448 448 kgMocrenIO->addTrack(tracks, colors); … … 454 454 455 455 if(GFDEBUG_DET) G4cout << ">>>>>>>>>>>>>>>>>>>>>> ("; 456 std::vector< float> transformObjects;457 for( int i = 0; i < 3; i++) {456 std::vector<G4float> transformObjects; 457 for(G4int i = 0; i < 3; i++) { 458 458 // need to check!! 459 459 transformObjects.push_back((kVolumeSize[i]/2. - kVoxelDimension[i]/2.)); … … 533 533 534 534 if(GFDEBUG_TRK) G4cout << " trajectory points : " << G4endl; 535 std::vector< float *> trajectory;535 std::vector<G4float *> trajectory; 536 536 if(polyline.size() < 2) return; 537 537 G4Polyline::const_iterator preitr = polyline.begin(); … … 544 544 postPts -= trans; 545 545 postPts.transform(rot); 546 float * stepPts = newfloat[6];546 G4float * stepPts = new G4float[6]; 547 547 stepPts[0] = prePts.x(); 548 548 stepPts[1] = prePts.y(); … … 657 657 658 658 //---------- (3) Facet block 659 for ( int f = polyhedron.GetNoFacets(); f; f--){659 for (G4int f = polyhedron.GetNoFacets(); f; f--){ 660 660 G4int notLastEdge; 661 661 G4int index = -1; // initialization … … 764 764 G4Polyhedron * poly = box.CreatePolyhedron(); 765 765 poly->Transform(*fpObjectTransformation); 766 // int nv = poly->GetNoVertices();766 //G4int nv = poly->GetNoVertices(); 767 767 G4Point3D v1, v2; 768 768 G4int next; 769 769 //while(1) { // next flag isn't functional. 770 for( int i = 0; i < 12; i++) { // # of edges is 12.770 for(G4int i = 0; i < 12; i++) { // # of edges is 12. 771 771 poly->GetNextEdge(v1, v2, next); 772 772 if(next == 0) break; … … 927 927 } 928 928 929 for( int i = 0; i < 3; i++) {929 for(G4int i = 0; i < 3; i++) { 930 930 kNestedVolumeDimension[i] = nDaughters[i]; 931 931 //kNestedVolumeDimension[i] = nDaughters[dirAxis[i]]; … … 940 940 if(nestPara) { 941 941 G4double prexyz[3] = {0.,0.,0.}, xyz[3] = {0.,0.,0.}; 942 for( int n0 = 0; n0 < nDaughters[0]; n0++) {943 for( int n1 = 0; n1 < nDaughters[1]; n1++) {944 for( int n2 = 0; n2 < nDaughters[2]; n2++) {942 for(G4int n0 = 0; n0 < nDaughters[0]; n0++) { 943 for(G4int n1 = 0; n1 < nDaughters[1]; n1++) { 944 for(G4int n2 = 0; n2 < nDaughters[2]; n2++) { 945 945 946 946 G4GMocrenTouchable * touch = new G4GMocrenTouchable(n1, n0); … … 961 961 xyz[2] = tbox.GetZHalfLength()/mm; 962 962 if(n0 != 0 || n1 != 0 || n2 != 0) { 963 for( int i = 0; i < 3; i++) {963 for(G4int i = 0; i < 3; i++) { 964 964 if(xyz[i] != prexyz[i]) G4Exception("Error[gMocrenFileSceneHandler]: Unsupported parameterisation."); 965 965 } … … 980 980 << " density: " << dens << G4endl; 981 981 982 for( int i = 0; i < 3; i++) prexyz[i] = xyz[i];982 for(G4int i = 0; i < 3; i++) prexyz[i] = xyz[i]; 983 983 } 984 984 } … … 990 990 // mesh size 991 991 if(!kbSetModalityVoxelSize) { 992 float spacing[3] = {2*xyz[0], 2*xyz[1], 2*xyz[2]}; 992 G4float spacing[3] = {static_cast<G4float>(2*xyz[0]), 993 static_cast<G4float>(2*xyz[1]), 994 static_cast<G4float>(2*xyz[2])}; 993 995 kgMocrenIO->setVoxelSpacing(spacing); 994 996 kVoxelDimension.set(spacing[0], spacing[1], spacing[2]); … … 1014 1016 G4cout << " physical volume node id : " 1015 1017 << "size: " << npvp << ", PV name: "; 1016 for( int i = 0; i < npvp; i++) {1018 for(G4int i = 0; i < npvp; i++) { 1017 1019 G4cout << pPVModel->GetDrawnPVPath()[i].GetPhysicalVolume()->GetName() 1018 1020 << " [param:" … … 1093 1095 G4int nXY = kNestedVolumeDimension[0]*kNestedVolumeDimension[1]; 1094 1096 1095 for( int n0 = 0; n0 < kNestedVolumeDimension[0]; n0++) {1096 for( int n1 = 0; n1 < kNestedVolumeDimension[1]; n1++) {1097 for( int n2 = 0; n2 < kNestedVolumeDimension[2]; n2++) {1097 for(G4int n0 = 0; n0 < kNestedVolumeDimension[0]; n0++) { 1098 for(G4int n1 = 0; n1 < kNestedVolumeDimension[1]; n1++) { 1099 for(G4int n2 = 0; n2 < kNestedVolumeDimension[2]; n2++) { 1098 1100 1099 1101 G4int repNo = n0 + n1*nX + n2*nXY; … … 1123 1125 // mesh size 1124 1126 if(!kbSetModalityVoxelSize) { 1125 float spacing[3] = {2*phantomPara->GetVoxelHalfX(),1126 2*phantomPara->GetVoxelHalfY(),1127 2*phantomPara->GetVoxelHalfZ()};1127 G4float spacing[3] = {static_cast<G4float>(2*phantomPara->GetVoxelHalfX()), 1128 static_cast<G4float>(2*phantomPara->GetVoxelHalfY()), 1129 static_cast<G4float>(2*phantomPara->GetVoxelHalfZ())}; 1128 1130 kgMocrenIO->setVoxelSpacing(spacing); 1129 1131 kVoxelDimension.set(spacing[0], spacing[1], spacing[2]); … … 1158 1160 1159 1161 // get densities of the parameterized patient geometry 1160 for( int n0 = 0; n0 < kNestedVolumeDimension[0]; n0++) {1161 for( int n1 = 0; n1 < kNestedVolumeDimension[1]; n1++) {1162 for( int n2 = 0; n2 < kNestedVolumeDimension[2]; n2++) {1162 for(G4int n0 = 0; n0 < kNestedVolumeDimension[0]; n0++) { 1163 for(G4int n1 = 0; n1 < kNestedVolumeDimension[1]; n1++) { 1164 for(G4int n2 = 0; n2 < kNestedVolumeDimension[2]; n2++) { 1163 1165 1164 1166 G4double dens = 0.*(g/cm3); … … 1192 1194 // mesh size 1193 1195 if(!kbSetModalityVoxelSize) { 1194 float spacing[3] = {boxSize.x()*2/nVoxels[0],1195 boxSize.y()*2/nVoxels[1],1196 boxSize.z()*2/nVoxels[2]};1196 G4float spacing[3] = {static_cast<G4float>(boxSize.x()*2/nVoxels[0]), 1197 static_cast<G4float>(boxSize.y()*2/nVoxels[1]), 1198 static_cast<G4float>(boxSize.z()*2/nVoxels[2])}; 1197 1199 1198 1200 kgMocrenIO->setVoxelSpacing(spacing); … … 1292 1294 G4cout << " " << tubes.GetName() << G4endl; 1293 1295 G4Polyhedron * poly = tubes.CreatePolyhedron(); 1294 int nv = poly->GetNoVertices();1295 for( int i = 0; i < nv; i++) {1296 G4int nv = poly->GetNoVertices(); 1297 for(G4int i = 0; i < nv; i++) { 1296 1298 G4cout << " (" << poly->GetVertex(i).x() << ", " 1297 1299 << poly->GetVertex(i).y() << ", " … … 1449 1451 if(GFDEBUG_TRK) { 1450 1452 std::cout << " ::AddCompound(const G4VTrajectory&) >>>>>>>>> " << std::endl; 1451 1452 1453 G4TrajectoriesModel * pTrModel = dynamic_cast<G4TrajectoriesModel*>(fpModel); 1453 1454 if (!pTrModel) { … … 1464 1465 G4cout << " momentum: " << trj->GetInitialMomentum() << G4endl; 1465 1466 1466 int nPnt = trj->GetPointEntries();1467 G4int nPnt = trj->GetPointEntries(); 1467 1468 G4cout << " point: "; 1468 for( int i = 0; i < nPnt; i++) {1469 for(G4int i = 0; i < nPnt; i++) { 1469 1470 G4cout << trj->GetPoint(i)->GetPosition() << ", "; 1470 1471 } 1471 1472 G4cout << G4endl; 1472 1473 1474 } 1473 } 1474 G4cout << G4endl; 1475 1475 } 1476 1476 … … 1544 1544 // Get attributes 1545 1545 for(itr = attval->begin(); itr != attval->end(); itr++) { 1546 for( int i = 0; i < nhitname; i++) {1546 for(G4int i = 0; i < nhitname; i++) { 1547 1547 if(itr->GetName() == hitNames[i]) { 1548 1548 … … 1601 1601 1602 1602 1603 //for( int i = 0; i < nhitname; i++) { // this selection trusts1603 //for(G4int i = 0; i < nhitname; i++) { // this selection trusts 1604 1604 //if(scorername == hitScorerNames[i]) { // thea command /vis/scene/add/psHits hit_name. 1605 1605 … … 1630 1630 G4cout << " >>>>> " << meshname << " : " << scorername << G4endl; 1631 1631 1632 for( int i = 0; i < nhitname; i++)1632 for(G4int i = 0; i < nhitname; i++) 1633 1633 if(scorername == hitScorerNames[i]) 1634 1634 G4cout << " !!!! Hit scorer !!!! " << scorername << G4endl; … … 1702 1702 1703 1703 // edge points of the detector 1704 std::vector< float *> dedges;1704 std::vector<G4float *> dedges; 1705 1705 G4Polyhedron * poly = solid.CreatePolyhedron(); 1706 1706 detector.polyhedron = poly; … … 1717 1717 //uccolor[0] = uccolor[1] = uccolor[2] = 30; // dark grey 1718 1718 } 1719 for( int i = 0; i < 3; i++) detector.color[i] = uccolor[i];1719 for(G4int i = 0; i < 3; i++) detector.color[i] = uccolor[i]; 1720 1720 // 1721 1721 kDetectors.push_back(detector); 1722 1722 1723 1723 if(GFDEBUG_DET > 1) { 1724 G4cout << "0 color: (" << ( int)uccolor[0] << ", "1725 << ( int)uccolor[1] << ", " << (int)uccolor[2] << ")"1724 G4cout << "0 color: (" << (G4int)uccolor[0] << ", " 1725 << (G4int)uccolor[1] << ", " << (G4int)uccolor[2] << ")" 1726 1726 << G4endl; 1727 1727 } … … 1742 1742 1743 1743 // edge points of the detector 1744 std::vector< float *> dedges;1744 std::vector<G4float *> dedges; 1745 1745 G4Polyhedron * poly = itr->polyhedron; 1746 1746 poly->Transform(itr->transform3D); … … 1755 1755 while(bnext) { 1756 1756 if(!(poly->GetNextEdge(v1, v2, next))) bnext =false; 1757 float * edge = newfloat[6];1757 G4float * edge = new G4float[6]; 1758 1758 edge[0] = v1.x()/mm; 1759 1759 edge[1] = v1.y()/mm; … … 1772 1772 // 1773 1773 kgMocrenIO->addDetector(detname, dedges, uccolor); 1774 for( int i = 0; i < nedges; i++) { // # of edges is 12.1774 for(G4int i = 0; i < nedges; i++) { // # of edges is 12. 1775 1775 delete [] dedges[i]; 1776 1776 } … … 1778 1778 1779 1779 if(GFDEBUG_DET > 1) { 1780 G4cout << " color: (" << ( int)uccolor[0] << ", "1781 << ( int)uccolor[1] << ", " << (int)uccolor[2] << ")"1780 G4cout << " color: (" << (G4int)uccolor[0] << ", " 1781 << (G4int)uccolor[1] << ", " << (G4int)uccolor[2] << ")" 1782 1782 << G4endl; 1783 1783 } … … 1789 1789 kNestedVolumeDimension[1] == 0 || 1790 1790 kNestedVolumeDimension[2] == 0) { 1791 for( int i = 0; i < 3; i++) _idx3d[i] = 0;1791 for(G4int i = 0; i < 3; i++) _idx3d[i] = 0; 1792 1792 return; 1793 1793 } -
trunk/source/visualization/management/History
r1258 r1274 1 $Id: History,v 1.14 2 2010/05/11 12:17:40allison Exp $1 $Id: History,v 1.143 2010/05/20 07:56:21 allison Exp $ 2 2 3 3 ------------------------------------------------------------------- … … 26 26 History file for visualization management sub-category 27 27 ------------------------------------------------------ 28 29 20th May 2010 John Allison (visman-V09-03-01) 30 - G4VisCommandsCompound.cc: Restore previous viewer after /vis/drawTree. 31 - G4VisManager.hh: Cosmetic. 32 - G4VGraphicsSystem: Add Set methods. 28 33 29 34 11th May 2010 John Allison (visman-V09-03-00) -
trunk/source/visualization/management/include/G4VGraphicsSystem.hh
r954 r1274 25 25 // 26 26 // 27 // $Id: G4VGraphicsSystem.hh,v 1.1 1 2006/06/29 21:28:04 gunterExp $27 // $Id: G4VGraphicsSystem.hh,v 1.12 2010/05/20 07:55:47 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 80 80 const G4String& GetDescription () const; 81 81 Functionality GetFunctionality () const; 82 void SetName (const G4String&); 83 void SetNickName (const G4String&); 84 void SetDescription (const G4String&); 85 void SetFunctionality (Functionality); 82 86 83 87 protected: 84 constG4String fName;85 constG4String fNickname;86 constG4String fDescription;88 G4String fName; 89 G4String fNickname; 90 G4String fDescription; 87 91 Functionality fFunctionality; 88 92 }; -
trunk/source/visualization/management/include/G4VGraphicsSystem.icc
r954 r1274 25 25 // 26 26 // 27 // $Id: G4VGraphicsSystem.icc,v 1. 7 2006/06/29 21:28:06 gunterExp $27 // $Id: G4VGraphicsSystem.icc,v 1.8 2010/05/20 07:55:47 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 48 48 return fFunctionality; 49 49 } 50 51 inline void G4VGraphicsSystem::SetName (const G4String& name) { 52 fName = name; 53 } 54 55 inline void G4VGraphicsSystem::SetNickName (const G4String& nickname) { 56 fNickname = nickname; 57 } 58 59 inline void G4VGraphicsSystem::SetDescription (const G4String& description) { 60 fDescription = description; 61 } 62 63 inline void G4VGraphicsSystem::SetFunctionality (Functionality f) { 64 fFunctionality = f; 65 } -
trunk/source/visualization/management/include/G4VisManager.hh
r933 r1274 25 25 // 26 26 // 27 // $Id: G4VisManager.hh,v 1.7 0 2009/02/25 18:28:00 lgarnierExp $27 // $Id: G4VisManager.hh,v 1.71 2010/05/20 07:54:31 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 // … … 366 366 const G4VisExtent& = G4VisExtent::NullExtent); 367 367 void SetUserActionExtent (const G4VisExtent&); 368 void SetCurrentGraphicsSystem (G4VGraphicsSystem* pSystem);368 void SetCurrentGraphicsSystem (G4VGraphicsSystem*); 369 369 void SetCurrentScene (G4Scene*); 370 void SetCurrentSceneHandler (G4VSceneHandler* pScene);371 void SetCurrentViewer (G4VViewer* pView);370 void SetCurrentSceneHandler (G4VSceneHandler*); 371 void SetCurrentViewer (G4VViewer*); 372 372 G4SceneHandlerList& SetAvailableSceneHandlers (); // Returns lvalue. 373 373 G4SceneList& SetSceneList (); // Returns lvalue. -
trunk/source/visualization/management/src/G4VisCommandsCompound.cc
r954 r1274 25 25 // 26 26 // 27 // $Id: G4VisCommandsCompound.cc,v 1. 39 2007/11/16 20:29:04 perlExp $27 // $Id: G4VisCommandsCompound.cc,v 1.40 2010/05/20 07:54:01 allison Exp $ 28 28 // GEANT4 tag $Name: $ 29 29 … … 66 66 is >> pvname >> system; 67 67 68 G4VGraphicsSystem* keepSystem = fpVisManager->GetCurrentGraphicsSystem(); 69 G4Scene* keepScene = fpVisManager->GetCurrentScene(); 70 G4VSceneHandler* keepSceneHandler = fpVisManager->GetCurrentSceneHandler(); 71 G4VViewer* keepViewer = fpVisManager->GetCurrentViewer(); 72 68 73 G4UImanager* UImanager = G4UImanager::GetUIpointer(); 69 74 G4int keepVerbose = UImanager->GetVerboseLevel(); … … 77 82 UImanager->ApplyCommand("/vis/viewer/flush"); 78 83 UImanager->SetVerboseLevel(keepVerbose); 84 85 if (keepViewer) { 86 if (fpVisManager->GetVerbosity() >= G4VisManager::warnings) { 87 G4cout << "Reverting to " << keepViewer->GetName() << G4endl; 88 } 89 fpVisManager->SetCurrentGraphicsSystem(keepSystem); 90 fpVisManager->SetCurrentScene(keepScene); 91 fpVisManager->SetCurrentSceneHandler(keepSceneHandler); 92 fpVisManager->SetCurrentViewer(keepViewer); 93 } 79 94 } 80 95 -
trunk/source/visualization/test/History
r1228 r1274 1 $Id: History,v 1.12 1 2009/11/06 16:02:33allison Exp $1 $Id: History,v 1.123 2010/05/11 12:06:08 allison Exp $ 2 2 3 3 History file for visualization/test subdirectory … … 5 5 6 6 $Log: History,v $ 7 Revision 1.123 2010/05/11 12:06:08 allison 8 vistest-V09-03-00 9 10 Revision 1.122 2010/05/11 12:04:39 allison 11 Added printEPS to test19.g4m, as suggested by Laurent. 12 7 13 Revision 1.121 2009/11/06 16:02:33 allison 8 14 vistest-V09-02-01 -
trunk/source/visualization/test/test19.g4m
r1138 r1274 41 41 #/vis/sceneHandler/create OGLSXm 42 42 #/vis/sceneHandler/create OGLIX 43 #/vis/sceneHandler/create OGLSX44 /vis/sceneHandler/create OGLSXm43 /vis/sceneHandler/create OGLSX 44 #/vis/sceneHandler/create OGLSXm 45 45 #/vis/sceneHandler/create VRML1 46 46 #/vis/sceneHandler/create VRML1FILE … … 71 71 # (all that happens is an extra refresh). 72 72 /vis/viewer/flush 73 /vis/ogl/set/printMode vectored 74 /vis/ogl/set/printSize 800 600 75 /vis/ogl/set/printFilename output-test19-1 76 /vis/ogl/printEPS 73 77 # 74 78 # Create another viewer. … … 80 84 # 81 85 /vis/viewer/flush 86 /vis/ogl/set/printMode vectored 87 /vis/ogl/set/printSize 800 600 88 /vis/ogl/set/printFilename output-test19-2 89 /vis/ogl/printEPS 82 90 # 83 91 # Now hidden line removal. … … 90 98 # 91 99 /vis/viewer/flush 100 /vis/ogl/set/printMode vectored 101 /vis/ogl/set/printSize 800 600 102 /vis/ogl/set/printFilename output-test19-3 103 /vis/ogl/printEPS 92 104 # 93 105 # Now hidden line *and* hidden surface removal. … … 100 112 # 101 113 /vis/viewer/flush 114 /vis/ogl/set/printMode vectored 115 /vis/ogl/set/printSize 800 600 116 /vis/ogl/set/printFilename output-test19-4 117 /vis/ogl/printEPS 102 118 # 103 119 # Start a run to initialise/optimise geometry and draw user-drawn transients. … … 112 128 /vis/scene/notifyHandlers 113 129 /vis/viewer/flush 130 /vis/ogl/set/printMode vectored 131 /vis/ogl/set/printSize 800 600 132 /vis/ogl/set/printFilename output-test19-5 133 /vis/ogl/printEPS 114 134 # 115 135 # Logical volume of Boolean solids... … … 122 142 /vis/scene/notifyHandlers 123 143 /vis/viewer/flush 144 /vis/ogl/set/printMode vectored 145 /vis/ogl/set/printSize 800 600 146 /vis/ogl/set/printFilename output-test19-6 147 /vis/ogl/printEPS 124 148 # 125 149 /vis/scene/create … … 129 153 /vis/viewer/set/viewpointThetaPhi 35 35 130 154 /vis/viewer/flush 155 /vis/ogl/set/printMode vectored 156 /vis/ogl/set/printSize 800 600 157 /vis/ogl/set/printFilename output-test19-7 158 /vis/ogl/printEPS 131 159 # 132 160 /vis/scene/create … … 136 164 /vis/viewer/set/viewpointThetaPhi 35 35 137 165 /vis/viewer/flush 166 /vis/ogl/set/printMode vectored 167 /vis/ogl/set/printSize 800 600 168 /vis/ogl/set/printFilename output-test19-8 169 /vis/ogl/printEPS 138 170 # 139 171 # Send geantino through... … … 153 185 /tracking/verbose 0 154 186 /vis/viewer/flush 187 /vis/ogl/set/printMode vectored 188 /vis/ogl/set/printSize 800 600 189 /vis/ogl/set/printFilename output-test19-9 190 /vis/ogl/printEPS 155 191 # 156 192 # Rotated tracker tube … … 172 208 /run/beamOn 173 209 /vis/viewer/flush 210 /vis/ogl/set/printMode vectored 211 /vis/ogl/set/printSize 800 600 212 /vis/ogl/set/printFilename output-test19-10 213 /vis/ogl/printEPS 174 214 # 175 215 # G4Trap1 … … 215 255 /run/beamOn 216 256 /vis/viewer/flush 257 /vis/ogl/set/printMode vectored 258 /vis/ogl/set/printSize 800 600 259 /vis/ogl/set/printFilename output-test19-11 260 /vis/ogl/printEPS 217 261 # 218 262 # G4Trap2 … … 241 285 /run/beamOn 242 286 /vis/viewer/flush 287 /vis/ogl/set/printMode vectored 288 /vis/ogl/set/printSize 800 600 289 /vis/ogl/set/printFilename output-test19-12 290 /vis/ogl/printEPS 243 291 # 244 292 # Displaced solid. … … 252 300 /run/beamOn 253 301 /vis/viewer/flush 302 /vis/ogl/set/printMode vectored 303 /vis/ogl/set/printSize 800 600 304 /vis/ogl/set/printFilename output-test19-13 305 /vis/ogl/printEPS 254 306 # 255 307 # Boolean solid. … … 313 365 /run/beamOn 314 366 /vis/viewer/flush 367 /vis/ogl/set/printMode vectored 368 /vis/ogl/set/printSize 800 600 369 /vis/ogl/set/printFilename output-test19-14 370 /vis/ogl/printEPS 315 371 # 316 372 # To view replicas... … … 355 411 /run/beamOn 356 412 /vis/viewer/flush 413 /vis/ogl/set/printMode vectored 414 /vis/ogl/set/printSize 800 600 415 /vis/ogl/set/printFilename output-test19-15 416 /vis/ogl/printEPS 357 417 #...end 358 418 # … … 360 420 /vis/viewer/set/projection perspective 30 361 421 /vis/viewer/flush 422 /vis/ogl/set/printMode vectored 423 /vis/ogl/set/printSize 800 600 424 /vis/ogl/set/printFilename output-test19-16 425 /vis/ogl/printEPS 362 426 # 363 427 #/vis/sceneHandler/create OIX … … 367 431 /vis/viewer/set/viewpointThetaPhi 30 30 368 432 /vis/viewer/flush 433 /vis/ogl/set/printMode vectored 434 /vis/ogl/set/printSize 800 600 435 /vis/ogl/set/printFilename output-test19-17 436 /vis/ogl/printEPS 369 437 # 370 438 # You can use /vis/rayTracer/... commands … … 378 446 /vis/viewer/set/viewpointThetaPhi 45 45 379 447 /vis/viewer/flush 448 /vis/ogl/set/printMode vectored 449 /vis/ogl/set/printSize 800 600 450 /vis/ogl/set/printFilename output-test19-18 451 /vis/ogl/printEPS 380 452 # 381 453 # Odd!!? JPEG image seems upside down for default view direction... 382 454 /vis/viewer/create ! ! 200 383 455 /vis/viewer/flush 456 /vis/ogl/set/printMode vectored 457 /vis/ogl/set/printSize 800 600 458 /vis/ogl/set/printFilename output-test19-19 459 /vis/ogl/printEPS 460 exit
Note: See TracChangeset
for help on using the changeset viewer.