From 3ff4ff90494ce95889d6745a59333b120da53ffa Mon Sep 17 00:00:00 2001 From: "Alexander V. Wolf" Date: Wed, 25 Dec 2024 09:11:23 +0700 Subject: [PATCH] Removed plugin Missing Stars The plugin is outdated after coming new star catalogs --- CMakeLists.txt | 1 - cmake/default_cfg.ini.cmake | 1 - plugins/MissingStars/CMakeLists.txt | 8 - plugins/MissingStars/COPYING | 340 ---- plugins/MissingStars/Doxyfile | 1800 ----------------- .../MissingStars/resources/MissingStars.qrc | 5 - .../MissingStars/resources/missingstars.json | 728 ------- plugins/MissingStars/src/CMakeLists.txt | 40 - plugins/MissingStars/src/MissingStar.cpp | 260 --- plugins/MissingStars/src/MissingStar.hpp | 120 -- plugins/MissingStars/src/MissingStars.cpp | 306 --- plugins/MissingStars/src/MissingStars.hpp | 164 -- .../src/gui/MissingStarsDialog.cpp | 105 - .../src/gui/MissingStarsDialog.hpp | 54 - .../src/gui/missingStarsDialog.ui | 83 - src/core/StelApp.cpp | 4 - src/gui/SearchDialog.cpp | 1 - 17 files changed, 4020 deletions(-) delete mode 100644 plugins/MissingStars/CMakeLists.txt delete mode 100644 plugins/MissingStars/COPYING delete mode 100644 plugins/MissingStars/Doxyfile delete mode 100644 plugins/MissingStars/resources/MissingStars.qrc delete mode 100644 plugins/MissingStars/resources/missingstars.json delete mode 100644 plugins/MissingStars/src/CMakeLists.txt delete mode 100644 plugins/MissingStars/src/MissingStar.cpp delete mode 100644 plugins/MissingStars/src/MissingStar.hpp delete mode 100644 plugins/MissingStars/src/MissingStars.cpp delete mode 100644 plugins/MissingStars/src/MissingStars.hpp delete mode 100644 plugins/MissingStars/src/gui/MissingStarsDialog.cpp delete mode 100644 plugins/MissingStars/src/gui/MissingStarsDialog.hpp delete mode 100644 plugins/MissingStars/src/gui/missingStarsDialog.ui diff --git a/CMakeLists.txt b/CMakeLists.txt index a8b1773556027..0e536eaed9ca7 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -541,7 +541,6 @@ ADD_PLUGIN(Calendars 1) ADD_PLUGIN(Exoplanets 1) ADD_PLUGIN(EquationOfTime 1) ADD_PLUGIN(MeteorShowers 1) -ADD_PLUGIN(MissingStars 0) ADD_PLUGIN(NavStars 1) ADD_PLUGIN(Novae 1) ADD_PLUGIN(Observability 1) diff --git a/cmake/default_cfg.ini.cmake b/cmake/default_cfg.ini.cmake index 72d1b4b8491d4..bbbd834d671f1 100644 --- a/cmake/default_cfg.ini.cmake +++ b/cmake/default_cfg.ini.cmake @@ -8,7 +8,6 @@ Satellites = true SolarSystemEditor = true Exoplanets = true MeteorShowers = true -MissingStars = true Novae = true FOV = true diff --git a/plugins/MissingStars/CMakeLists.txt b/plugins/MissingStars/CMakeLists.txt deleted file mode 100644 index 7a0f8e62b77a3..0000000000000 --- a/plugins/MissingStars/CMakeLists.txt +++ /dev/null @@ -1,8 +0,0 @@ -# This is the cmake config file for the Missing Stars plugin -# Further: Use program version number. (Static plugin, why bother?) -SET(MSP_VERSION "${VERSION}") - -ADD_DEFINITIONS(-DMISSINGSTARS_PLUGIN_VERSION="${MSP_VERSION}") -ADD_DEFINITIONS(-DMISSINGSTARS_PLUGIN_LICENSE="GNU GPLv2 or later") - -ADD_SUBDIRECTORY( src ) diff --git a/plugins/MissingStars/COPYING b/plugins/MissingStars/COPYING deleted file mode 100644 index b35f35c99338e..0000000000000 --- a/plugins/MissingStars/COPYING +++ /dev/null @@ -1,340 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 51 Franklin Street, Suite 500, Boston, MA 02110-1335 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335 USA - - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. diff --git a/plugins/MissingStars/Doxyfile b/plugins/MissingStars/Doxyfile deleted file mode 100644 index 651de051a96a8..0000000000000 --- a/plugins/MissingStars/Doxyfile +++ /dev/null @@ -1,1800 +0,0 @@ -# Doxyfile 1.8.0 - -# This file describes the settings to be used by the documentation system -# doxygen (www.doxygen.org) for a project. -# -# All text after a hash (#) is considered a comment and will be ignored. -# The format is: -# TAG = value [value, ...] -# For lists items can also be appended using: -# TAG += value [value, ...] -# Values that contain spaces should be placed between quotes (" "). - -#--------------------------------------------------------------------------- -# Project related configuration options -#--------------------------------------------------------------------------- - -# This tag specifies the encoding used for all characters in the config file -# that follow. The default is UTF-8 which is also the encoding used for all -# text before the first occurrence of this tag. Doxygen uses libiconv (or the -# iconv built into libc) for the transcoding. See -# http://www.gnu.org/software/libiconv for the list of possible encodings. - -DOXYFILE_ENCODING = UTF-8 - -# The PROJECT_NAME tag is a single word (or sequence of words) that should -# identify the project. Note that if you do not use Doxywizard you need -# to put quotes around the project name if it contains spaces. - -PROJECT_NAME = "Stellarium Missing Stars Plug-in" - -# The PROJECT_NUMBER tag can be used to enter a project or revision number. -# This could be handy for archiving the generated documentation or -# if some version control system is used. - -PROJECT_NUMBER = - -# Using the PROJECT_BRIEF tag one can provide an optional one line description -# for a project that appears at the top of each page and should give viewer -# a quick idea about the purpose of the project. Keep the description short. - -PROJECT_BRIEF = - -# With the PROJECT_LOGO tag one can specify an logo or icon that is -# included in the documentation. The maximum height of the logo should not -# exceed 55 pixels and the maximum width should not exceed 200 pixels. -# Doxygen will copy the logo to the output directory. - -PROJECT_LOGO = - -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) -# base path where the generated documentation will be put. -# If a relative path is entered, it will be relative to the location -# where doxygen was started. If left blank the current directory will be used. - -OUTPUT_DIRECTORY = - -# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create -# 4096 sub-directories (in 2 levels) under the output directory of each output -# format and will distribute the generated files over these directories. -# Enabling this option can be useful when feeding doxygen a huge amount of -# source files, where putting all generated files in the same directory would -# otherwise cause performance problems for the file system. - -CREATE_SUBDIRS = NO - -# The OUTPUT_LANGUAGE tag is used to specify the language in which all -# documentation generated by doxygen is written. Doxygen will use this -# information to generate all constant output in the proper language. -# The default language is English, other supported languages are: -# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, -# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, -# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English -# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, -# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, -# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. - -OUTPUT_LANGUAGE = English - -# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will -# include brief member descriptions after the members that are listed in -# the file and class documentation (similar to JavaDoc). -# Set to NO to disable this. - -BRIEF_MEMBER_DESC = YES - -# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend -# the brief description of a member or function before the detailed description. -# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the -# brief descriptions will be completely suppressed. - -REPEAT_BRIEF = YES - -# This tag implements a quasi-intelligent brief description abbreviator -# that is used to form the text in various listings. Each string -# in this list, if found as the leading text of the brief description, will be -# stripped from the text and the result after processing the whole list, is -# used as the annotated text. Otherwise, the brief description is used as-is. -# If left blank, the following values are used ("$name" is automatically -# replaced with the name of the entity): "The $name class" "The $name widget" -# "The $name file" "is" "provides" "specifies" "contains" -# "represents" "a" "an" "the" - -ABBREVIATE_BRIEF = - -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then -# Doxygen will generate a detailed section even if there is only a brief -# description. - -ALWAYS_DETAILED_SEC = NO - -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all -# inherited members of a class in the documentation of that class as if those -# members were ordinary class members. Constructors, destructors and assignment -# operators of the base classes will not be shown. - -INLINE_INHERITED_MEMB = NO - -# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full -# path before files name in the file list and in the header files. If set -# to NO the shortest path that makes the file name unique will be used. - -FULL_PATH_NAMES = NO - -# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag -# can be used to strip a user-defined part of the path. Stripping is -# only done if one of the specified strings matches the left-hand part of -# the path. The tag can be used to show relative paths in the file list. -# If left blank the directory from which doxygen is run is used as the -# path to strip. - -STRIP_FROM_PATH = - -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of -# the path mentioned in the documentation of a class, which tells -# the reader which header file to include in order to use a class. -# If left blank only the name of the header file containing the class -# definition is used. Otherwise one should specify the include paths that -# are normally passed to the compiler using the -I flag. - -STRIP_FROM_INC_PATH = - -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter -# (but less readable) file names. This can be useful if your file system -# doesn't support long names like on DOS, Mac, or CD-ROM. - -SHORT_NAMES = NO - -# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen -# will interpret the first line (until the first dot) of a JavaDoc-style -# comment as the brief description. If set to NO, the JavaDoc -# comments will behave just like regular Qt-style comments -# (thus requiring an explicit @brief command for a brief description.) - -JAVADOC_AUTOBRIEF = YES - -# If the QT_AUTOBRIEF tag is set to YES then Doxygen will -# interpret the first line (until the first dot) of a Qt-style -# comment as the brief description. If set to NO, the comments -# will behave just like regular Qt-style comments (thus requiring -# an explicit \brief command for a brief description.) - -QT_AUTOBRIEF = YES - -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen -# treat a multi-line C++ special comment block (i.e. a block of //! or /// -# comments) as a brief description. This used to be the default behaviour. -# The new default is to treat a multi-line C++ comment block as a detailed -# description. Set this tag to YES if you prefer the old behaviour instead. - -MULTILINE_CPP_IS_BRIEF = NO - -# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented -# member inherits the documentation from any documented member that it -# re-implements. - -INHERIT_DOCS = YES - -# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce -# a new page for each member. If set to NO, the documentation of a member will -# be part of the file/class/namespace that contains it. - -SEPARATE_MEMBER_PAGES = NO - -# The TAB_SIZE tag can be used to set the number of spaces in a tab. -# Doxygen uses this value to replace tabs by spaces in code fragments. - -TAB_SIZE = 8 - -# This tag can be used to specify a number of aliases that acts -# as commands in the documentation. An alias has the form "name=value". -# For example adding "sideeffect=\par Side Effects:\n" will allow you to -# put the command \sideeffect (or @sideeffect) in the documentation, which -# will result in a user-defined paragraph with heading "Side Effects:". -# You can put \n's in the value part of an alias to insert newlines. - -ALIASES = - -# This tag can be used to specify a number of word-keyword mappings (TCL only). -# A mapping has the form "name=value". For example adding -# "class=itcl::class" will allow you to use the command class in the -# itcl::class meaning. - -TCL_SUBST = - -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C -# sources only. Doxygen will then generate output that is more tailored for C. -# For instance, some of the names that are used will be different. The list -# of all members will be omitted, etc. - -OPTIMIZE_OUTPUT_FOR_C = NO - -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java -# sources only. Doxygen will then generate output that is more tailored for -# Java. For instance, namespaces will be presented as packages, qualified -# scopes will look different, etc. - -OPTIMIZE_OUTPUT_JAVA = NO - -# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran -# sources only. Doxygen will then generate output that is more tailored for -# Fortran. - -OPTIMIZE_FOR_FORTRAN = NO - -# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL -# sources. Doxygen will then generate output that is tailored for -# VHDL. - -OPTIMIZE_OUTPUT_VHDL = NO - -# Doxygen selects the parser to use depending on the extension of the files it -# parses. With this tag you can assign which parser to use for a given extension. -# Doxygen has a built-in mapping, but you can override or extend it using this -# tag. The format is ext=language, where ext is a file extension, and language -# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, -# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make -# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C -# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions -# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. - -EXTENSION_MAPPING = - -# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all -# comments according to the Markdown format, which allows for more readable -# documentation. See http://daringfireball.net/projects/markdown/ for details. -# The output of markdown processing is further processed by doxygen, so you -# can mix doxygen, HTML, and XML commands with Markdown formatting. -# Disable only in case of backward compatibilities issues. - -MARKDOWN_SUPPORT = YES - -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want -# to include (a tag file for) the STL sources as input, then you should -# set this tag to YES in order to let doxygen match functions declarations and -# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. -# func(std::string) {}). This also makes the inheritance and collaboration -# diagrams that involve STL classes more complete and accurate. - -BUILTIN_STL_SUPPORT = NO - -# If you use Microsoft's C++/CLI language, you should set this option to YES to -# enable parsing support. - -CPP_CLI_SUPPORT = NO - -# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. -# Doxygen will parse them like normal C++ but will assume all classes use public -# instead of private inheritance when no explicit protection keyword is present. - -SIP_SUPPORT = NO - -# For Microsoft's IDL there are propget and propput attributes to indicate getter -# and setter methods for a property. Setting this option to YES (the default) -# will make doxygen replace the get and set methods by a property in the -# documentation. This will only work if the methods are indeed getting or -# setting a simple type. If this is not the case, or you want to show the -# methods anyway, you should set this option to NO. - -IDL_PROPERTY_SUPPORT = YES - -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC -# tag is set to YES, then doxygen will reuse the documentation of the first -# member in the group (if any) for the other members of the group. By default -# all members of a group must be documented explicitly. - -DISTRIBUTE_GROUP_DOC = NO - -# Set the SUBGROUPING tag to YES (the default) to allow class member groups of -# the same type (for instance a group of public functions) to be put as a -# subgroup of that type (e.g. under the Public Functions section). Set it to -# NO to prevent subgrouping. Alternatively, this can be done per class using -# the \nosubgrouping command. - -SUBGROUPING = YES - -# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and -# unions are shown inside the group in which they are included (e.g. using -# @ingroup) instead of on a separate page (for HTML and Man pages) or -# section (for LaTeX and RTF). - -INLINE_GROUPED_CLASSES = NO - -# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and -# unions with only public data fields will be shown inline in the documentation -# of the scope in which they are defined (i.e. file, namespace, or group -# documentation), provided this scope is documented. If set to NO (the default), -# structs, classes, and unions are shown on a separate page (for HTML and Man -# pages) or section (for LaTeX and RTF). - -INLINE_SIMPLE_STRUCTS = NO - -# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum -# is documented as struct, union, or enum with the name of the typedef. So -# typedef struct TypeS {} TypeT, will appear in the documentation as a struct -# with name TypeT. When disabled the typedef will appear as a member of a file, -# namespace, or class. And the struct will be named TypeS. This can typically -# be useful for C code in case the coding convention dictates that all compound -# types are typedef'ed and only the typedef is referenced, never the tag name. - -TYPEDEF_HIDES_STRUCT = NO - -# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to -# determine which symbols to keep in memory and which to flush to disk. -# When the cache is full, less often used symbols will be written to disk. -# For small to medium size projects (<1000 input files) the default value is -# probably good enough. For larger projects a too small cache size can cause -# doxygen to be busy swapping symbols to and from disk most of the time -# causing a significant performance penalty. -# If the system has enough physical memory increasing the cache will improve the -# performance by keeping more symbols in memory. Note that the value works on -# a logarithmic scale so increasing the size by one will roughly double the -# memory usage. The cache size is given by this formula: -# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, -# corresponding to a cache size of 2^16 = 65536 symbols. - -SYMBOL_CACHE_SIZE = 0 - -# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be -# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given -# their name and scope. Since this can be an expensive process and often the -# same symbol appear multiple times in the code, doxygen keeps a cache of -# pre-resolved symbols. If the cache is too small doxygen will become slower. -# If the cache is too large, memory is wasted. The cache size is given by this -# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, -# corresponding to a cache size of 2^16 = 65536 symbols. - -LOOKUP_CACHE_SIZE = 0 - -#--------------------------------------------------------------------------- -# Build related configuration options -#--------------------------------------------------------------------------- - -# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in -# documentation are documented, even if no documentation was available. -# Private class members and static file members will be hidden unless -# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES - -EXTRACT_ALL = YES - -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class -# will be included in the documentation. - -EXTRACT_PRIVATE = YES - -# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. - -EXTRACT_PACKAGE = NO - -# If the EXTRACT_STATIC tag is set to YES all static members of a file -# will be included in the documentation. - -EXTRACT_STATIC = YES - -# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) -# defined locally in source files will be included in the documentation. -# If set to NO only classes defined in header files are included. - -EXTRACT_LOCAL_CLASSES = YES - -# This flag is only useful for Objective-C code. When set to YES local -# methods, which are defined in the implementation section but not in -# the interface are included in the documentation. -# If set to NO (the default) only methods in the interface are included. - -EXTRACT_LOCAL_METHODS = NO - -# If this flag is set to YES, the members of anonymous namespaces will be -# extracted and appear in the documentation as a namespace called -# 'anonymous_namespace{file}', where file will be replaced with the base -# name of the file that contains the anonymous namespace. By default -# anonymous namespaces are hidden. - -EXTRACT_ANON_NSPACES = NO - -# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all -# undocumented members of documented classes, files or namespaces. -# If set to NO (the default) these members will be included in the -# various overviews, but no documentation section is generated. -# This option has no effect if EXTRACT_ALL is enabled. - -HIDE_UNDOC_MEMBERS = NO - -# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all -# undocumented classes that are normally visible in the class hierarchy. -# If set to NO (the default) these classes will be included in the various -# overviews. This option has no effect if EXTRACT_ALL is enabled. - -HIDE_UNDOC_CLASSES = NO - -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all -# friend (class|struct|union) declarations. -# If set to NO (the default) these declarations will be included in the -# documentation. - -HIDE_FRIEND_COMPOUNDS = NO - -# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any -# documentation blocks found inside the body of a function. -# If set to NO (the default) these blocks will be appended to the -# function's detailed documentation block. - -HIDE_IN_BODY_DOCS = NO - -# The INTERNAL_DOCS tag determines if documentation -# that is typed after a \internal command is included. If the tag is set -# to NO (the default) then the documentation will be excluded. -# Set it to YES to include the internal documentation. - -INTERNAL_DOCS = NO - -# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate -# file names in lower-case letters. If set to YES upper-case letters are also -# allowed. This is useful if you have classes or files whose names only differ -# in case and if your file system supports case sensitive file names. Windows -# and Mac users are advised to set this option to NO. - -CASE_SENSE_NAMES = YES - -# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen -# will show members with their full class and namespace scopes in the -# documentation. If set to YES the scope will be hidden. - -HIDE_SCOPE_NAMES = NO - -# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen -# will put a list of the files that are included by a file in the documentation -# of that file. - -SHOW_INCLUDE_FILES = YES - -# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen -# will list include files with double quotes in the documentation -# rather than with sharp brackets. - -FORCE_LOCAL_INCLUDES = NO - -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] -# is inserted in the documentation for inline members. - -INLINE_INFO = YES - -# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen -# will sort the (detailed) documentation of file and class members -# alphabetically by member name. If set to NO the members will appear in -# declaration order. - -SORT_MEMBER_DOCS = YES - -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the -# brief documentation of file, namespace and class members alphabetically -# by member name. If set to NO (the default) the members will appear in -# declaration order. - -SORT_BRIEF_DOCS = NO - -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen -# will sort the (brief and detailed) documentation of class members so that -# constructors and destructors are listed first. If set to NO (the default) -# the constructors will appear in the respective orders defined by -# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. -# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO -# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. - -SORT_MEMBERS_CTORS_1ST = NO - -# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the -# hierarchy of group names into alphabetical order. If set to NO (the default) -# the group names will appear in their defined order. - -SORT_GROUP_NAMES = NO - -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be -# sorted by fully-qualified names, including namespaces. If set to -# NO (the default), the class list will be sorted only by class name, -# not including the namespace part. -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. -# Note: This option applies only to the class list, not to the -# alphabetical list. - -SORT_BY_SCOPE_NAME = NO - -# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to -# do proper type resolution of all parameters of a function it will reject a -# match between the prototype and the implementation of a member function even -# if there is only one candidate or it is obvious which candidate to choose -# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen -# will still accept a match between prototype and implementation in such cases. - -STRICT_PROTO_MATCHING = NO - -# The GENERATE_TODOLIST tag can be used to enable (YES) or -# disable (NO) the todo list. This list is created by putting \todo -# commands in the documentation. - -GENERATE_TODOLIST = YES - -# The GENERATE_TESTLIST tag can be used to enable (YES) or -# disable (NO) the test list. This list is created by putting \test -# commands in the documentation. - -GENERATE_TESTLIST = YES - -# The GENERATE_BUGLIST tag can be used to enable (YES) or -# disable (NO) the bug list. This list is created by putting \bug -# commands in the documentation. - -GENERATE_BUGLIST = YES - -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or -# disable (NO) the deprecated list. This list is created by putting -# \deprecated commands in the documentation. - -GENERATE_DEPRECATEDLIST= YES - -# The ENABLED_SECTIONS tag can be used to enable conditional -# documentation sections, marked by \if sectionname ... \endif. - -ENABLED_SECTIONS = - -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines -# the initial value of a variable or macro consists of for it to appear in -# the documentation. If the initializer consists of more lines than specified -# here it will be hidden. Use a value of 0 to hide initializers completely. -# The appearance of the initializer of individual variables and macros in the -# documentation can be controlled using \showinitializer or \hideinitializer -# command in the documentation regardless of this setting. - -MAX_INITIALIZER_LINES = 30 - -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated -# at the bottom of the documentation of classes and structs. If set to YES the -# list will mention the files that were used to generate the documentation. - -SHOW_USED_FILES = YES - -# If the sources in your project are distributed over multiple directories -# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy -# in the documentation. The default is NO. - -SHOW_DIRECTORIES = NO - -# Set the SHOW_FILES tag to NO to disable the generation of the Files page. -# This will remove the Files entry from the Quick Index and from the -# Folder Tree View (if specified). The default is YES. - -SHOW_FILES = YES - -# Set the SHOW_NAMESPACES tag to NO to disable the generation of the -# Namespaces page. -# This will remove the Namespaces entry from the Quick Index -# and from the Folder Tree View (if specified). The default is YES. - -SHOW_NAMESPACES = YES - -# The FILE_VERSION_FILTER tag can be used to specify a program or script that -# doxygen should invoke to get the current version for each file (typically from -# the version control system). Doxygen will invoke the program by executing (via -# popen()) the command , where is the value of -# the FILE_VERSION_FILTER tag, and is the name of an input file -# provided by doxygen. Whatever the program writes to standard output -# is used as the file version. See the manual for examples. - -FILE_VERSION_FILTER = - -# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed -# by doxygen. The layout file controls the global structure of the generated -# output files in an output format independent way. The create the layout file -# that represents doxygen's defaults, run doxygen with the -l option. -# You can optionally specify a file name after the option, if omitted -# DoxygenLayout.xml will be used as the name of the layout file. - -LAYOUT_FILE = - -# The CITE_BIB_FILES tag can be used to specify one or more bib files -# containing the references data. This must be a list of .bib files. The -# .bib extension is automatically appended if omitted. Using this command -# requires the bibtex tool to be installed. See also -# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style -# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this -# feature you need bibtex and perl available in the search path. - -CITE_BIB_FILES = - -#--------------------------------------------------------------------------- -# configuration options related to warning and progress messages -#--------------------------------------------------------------------------- - -# The QUIET tag can be used to turn on/off the messages that are generated -# by doxygen. Possible values are YES and NO. If left blank NO is used. - -QUIET = NO - -# The WARNINGS tag can be used to turn on/off the warning messages that are -# generated by doxygen. Possible values are YES and NO. If left blank -# NO is used. - -WARNINGS = YES - -# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings -# for undocumented members. If EXTRACT_ALL is set to YES then this flag will -# automatically be disabled. - -WARN_IF_UNDOCUMENTED = YES - -# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for -# potential errors in the documentation, such as not documenting some -# parameters in a documented function, or documenting parameters that -# don't exist or using markup commands wrongly. - -WARN_IF_DOC_ERROR = YES - -# The WARN_NO_PARAMDOC option can be enabled to get warnings for -# functions that are documented, but have no documentation for their parameters -# or return value. If set to NO (the default) doxygen will only warn about -# wrong or incomplete parameter documentation, but not about the absence of -# documentation. - -WARN_NO_PARAMDOC = NO - -# The WARN_FORMAT tag determines the format of the warning messages that -# doxygen can produce. The string should contain the $file, $line, and $text -# tags, which will be replaced by the file and line number from which the -# warning originated and the warning text. Optionally the format may contain -# $version, which will be replaced by the version of the file (if it could -# be obtained via FILE_VERSION_FILTER) - -WARN_FORMAT = "$file:$line: $text" - -# The WARN_LOGFILE tag can be used to specify a file to which warning -# and error messages should be written. If left blank the output is written -# to stderr. - -WARN_LOGFILE = - -#--------------------------------------------------------------------------- -# configuration options related to the input files -#--------------------------------------------------------------------------- - -# The INPUT tag can be used to specify the files and/or directories that contain -# documented source files. You may enter file names like "myfile.cpp" or -# directories like "/usr/src/myproject". Separate the files or directories -# with spaces. - -INPUT = ./src ./src/gui - -# This tag can be used to specify the character encoding of the source files -# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is -# also the default input encoding. Doxygen uses libiconv (or the iconv built -# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for -# the list of possible encodings. - -INPUT_ENCODING = UTF-8 - -# If the value of the INPUT tag contains directories, you can use the -# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left -# blank the following patterns are tested: -# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh -# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py -# *.f90 *.f *.for *.vhd *.vhdl - -FILE_PATTERNS = - -# The RECURSIVE tag can be used to turn specify whether or not subdirectories -# should be searched for input files as well. Possible values are YES and NO. -# If left blank NO is used. - -RECURSIVE = NO - -# The EXCLUDE tag can be used to specify files and/or directories that should be -# excluded from the INPUT source files. This way you can easily exclude a -# subdirectory from a directory tree whose root is specified with the INPUT tag. -# Note that relative paths are relative to the directory from which doxygen is -# run. - -EXCLUDE = - -# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or -# directories that are symbolic links (a Unix file system feature) are excluded -# from the input. - -EXCLUDE_SYMLINKS = NO - -# If the value of the INPUT tag contains directories, you can use the -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude -# certain files from those directories. Note that the wildcards are matched -# against the file with absolute path, so to exclude all test directories -# for example use the pattern */test/* - -EXCLUDE_PATTERNS = - -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names -# (namespaces, classes, functions, etc.) that should be excluded from the -# output. The symbol name can be a fully qualified name, a word, or if the -# wildcard * is used, a substring. Examples: ANamespace, AClass, -# AClass::ANamespace, ANamespace::*Test - -EXCLUDE_SYMBOLS = - -# The EXAMPLE_PATH tag can be used to specify one or more files or -# directories that contain example code fragments that are included (see -# the \include command). - -EXAMPLE_PATH = - -# If the value of the EXAMPLE_PATH tag contains directories, you can use the -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left -# blank all files are included. - -EXAMPLE_PATTERNS = - -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude -# commands irrespective of the value of the RECURSIVE tag. -# Possible values are YES and NO. If left blank NO is used. - -EXAMPLE_RECURSIVE = NO - -# The IMAGE_PATH tag can be used to specify one or more files or -# directories that contain image that are included in the documentation (see -# the \image command). - -IMAGE_PATH = - -# The INPUT_FILTER tag can be used to specify a program that doxygen should -# invoke to filter for each input file. Doxygen will invoke the filter program -# by executing (via popen()) the command , where -# is the value of the INPUT_FILTER tag, and is the name of an -# input file. Doxygen will then use the output that the filter program writes -# to standard output. -# If FILTER_PATTERNS is specified, this tag will be -# ignored. - -INPUT_FILTER = - -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern -# basis. -# Doxygen will compare the file name with each pattern and apply the -# filter if there is a match. -# The filters are a list of the form: -# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further -# info on how filters are used. If FILTER_PATTERNS is empty or if -# non of the patterns match the file name, INPUT_FILTER is applied. - -FILTER_PATTERNS = - -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using -# INPUT_FILTER) will be used to filter the input files when producing source -# files to browse (i.e. when SOURCE_BROWSER is set to YES). - -FILTER_SOURCE_FILES = NO - -# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file -# pattern. A pattern will override the setting for FILTER_PATTERN (if any) -# and it is also possible to disable source filtering for a specific pattern -# using *.ext= (so without naming a filter). This option only has effect when -# FILTER_SOURCE_FILES is enabled. - -FILTER_SOURCE_PATTERNS = - -#--------------------------------------------------------------------------- -# configuration options related to source browsing -#--------------------------------------------------------------------------- - -# If the SOURCE_BROWSER tag is set to YES then a list of source files will -# be generated. Documented entities will be cross-referenced with these sources. -# Note: To get rid of all source code in the generated output, make sure also -# VERBATIM_HEADERS is set to NO. - -SOURCE_BROWSER = NO - -# Setting the INLINE_SOURCES tag to YES will include the body -# of functions and classes directly in the documentation. - -INLINE_SOURCES = NO - -# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct -# doxygen to hide any special comment blocks from generated source code -# fragments. Normal C and C++ comments will always remain visible. - -STRIP_CODE_COMMENTS = YES - -# If the REFERENCED_BY_RELATION tag is set to YES -# then for each documented function all documented -# functions referencing it will be listed. - -REFERENCED_BY_RELATION = NO - -# If the REFERENCES_RELATION tag is set to YES -# then for each documented function all documented entities -# called/used by that function will be listed. - -REFERENCES_RELATION = NO - -# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) -# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from -# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will -# link to the source code. -# Otherwise they will link to the documentation. - -REFERENCES_LINK_SOURCE = YES - -# If the USE_HTAGS tag is set to YES then the references to source code -# will point to the HTML generated by the htags(1) tool instead of doxygen -# built-in source browser. The htags tool is part of GNU's global source -# tagging system (see http://www.gnu.org/software/global/global.html). You -# will need version 4.8.6 or higher. - -USE_HTAGS = NO - -# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen -# will generate a verbatim copy of the header file for each class for -# which an include is specified. Set to NO to disable this. - -VERBATIM_HEADERS = YES - -#--------------------------------------------------------------------------- -# configuration options related to the alphabetical class index -#--------------------------------------------------------------------------- - -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index -# of all compounds will be generated. Enable this if the project -# contains a lot of classes, structs, unions or interfaces. - -ALPHABETICAL_INDEX = YES - -# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then -# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns -# in which this list will be split (can be a number in the range [1..20]) - -COLS_IN_ALPHA_INDEX = 5 - -# In case all classes in a project start with a common prefix, all -# classes will be put under the same header in the alphabetical index. -# The IGNORE_PREFIX tag can be used to specify one or more prefixes that -# should be ignored while generating the index headers. - -IGNORE_PREFIX = - -#--------------------------------------------------------------------------- -# configuration options related to the HTML output -#--------------------------------------------------------------------------- - -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will -# generate HTML output. - -GENERATE_HTML = YES - -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `html' will be used as the default path. - -HTML_OUTPUT = html - -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for -# each generated HTML page (for example: .htm,.php,.asp). If it is left blank -# doxygen will generate files with .html extension. - -HTML_FILE_EXTENSION = .html - -# The HTML_HEADER tag can be used to specify a personal HTML header for -# each generated HTML page. If it is left blank doxygen will generate a -# standard header. Note that when using a custom header you are responsible -# for the proper inclusion of any scripts and style sheets that doxygen -# needs, which is dependent on the configuration options used. -# It is advised to generate a default header using "doxygen -w html -# header.html footer.html stylesheet.css YourConfigFile" and then modify -# that header. Note that the header is subject to change so you typically -# have to redo this when upgrading to a newer version of doxygen or when -# changing the value of configuration settings such as GENERATE_TREEVIEW! - -HTML_HEADER = - -# The HTML_FOOTER tag can be used to specify a personal HTML footer for -# each generated HTML page. If it is left blank doxygen will generate a -# standard footer. - -HTML_FOOTER = - -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading -# style sheet that is used by each HTML page. It can be used to -# fine-tune the look of the HTML output. If the tag is left blank doxygen -# will generate a default style sheet. Note that doxygen will try to copy -# the style sheet file to the HTML output directory, so don't put your own -# style sheet in the HTML output directory as well, or it will be erased! - -HTML_STYLESHEET = - -# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or -# other source files which should be copied to the HTML output directory. Note -# that these files will be copied to the base HTML output directory. Use the -# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these -# files. In the HTML_STYLESHEET file, use the file name only. Also note that -# the files will be copied as-is; there are no commands or markers available. - -HTML_EXTRA_FILES = - -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. -# Doxygen will adjust the colors in the style sheet and background images -# according to this color. Hue is specified as an angle on a colorwheel, -# see http://en.wikipedia.org/wiki/Hue for more information. -# For instance the value 0 represents red, 60 is yellow, 120 is green, -# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. -# The allowed range is 0 to 359. - -HTML_COLORSTYLE_HUE = 220 - -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of -# the colors in the HTML output. For a value of 0 the output will use -# grayscales only. A value of 255 will produce the most vivid colors. - -HTML_COLORSTYLE_SAT = 100 - -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to -# the luminance component of the colors in the HTML output. Values below -# 100 gradually make the output lighter, whereas values above 100 make -# the output darker. The value divided by 100 is the actual gamma applied, -# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, -# and 100 does not change the gamma. - -HTML_COLORSTYLE_GAMMA = 80 - -# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML -# page will contain the date and time when the page was generated. Setting -# this to NO can help when comparing the output of multiple runs. - -HTML_TIMESTAMP = YES - -# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, -# files or namespaces will be aligned in HTML using tables. If set to -# NO a bullet list will be used. - -HTML_ALIGN_MEMBERS = YES - -# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML -# documentation will contain sections that can be hidden and shown after the -# page has loaded. For this to work a browser that supports -# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox -# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). - -HTML_DYNAMIC_SECTIONS = NO - -# If the GENERATE_DOCSET tag is set to YES, additional index files -# will be generated that can be used as input for Apple's Xcode 3 -# integrated development environment, introduced with OSX 10.5 (Leopard). -# To create a documentation set, doxygen will generate a Makefile in the -# HTML output directory. Running make will produce the docset in that -# directory and running "make install" will install the docset in -# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find -# it at startup. -# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html -# for more information. - -GENERATE_DOCSET = NO - -# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the -# feed. A documentation feed provides an umbrella under which multiple -# documentation sets from a single provider (such as a company or product suite) -# can be grouped. - -DOCSET_FEEDNAME = "Doxygen generated docs" - -# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that -# should uniquely identify the documentation set bundle. This should be a -# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen -# will append .docset to the name. - -DOCSET_BUNDLE_ID = org.doxygen.Project - -# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify -# the documentation publisher. This should be a reverse domain-name style -# string, e.g. com.mycompany.MyDocSet.documentation. - -DOCSET_PUBLISHER_ID = org.doxygen.Publisher - -# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. - -DOCSET_PUBLISHER_NAME = Publisher - -# If the GENERATE_HTMLHELP tag is set to YES, additional index files -# will be generated that can be used as input for tools like the -# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) -# of the generated HTML documentation. - -GENERATE_HTMLHELP = NO - -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can -# be used to specify the file name of the resulting .chm file. You -# can add a path in front of the file if the result should not be -# written to the html output directory. - -CHM_FILE = - -# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can -# be used to specify the location (absolute path including file name) of -# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run -# the HTML help compiler on the generated index.hhp. - -HHC_LOCATION = - -# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag -# controls if a separate .chi index file is generated (YES) or that -# it should be included in the master .chm file (NO). - -GENERATE_CHI = NO - -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING -# is used to encode HtmlHelp index (hhk), content (hhc) and project file -# content. - -CHM_INDEX_ENCODING = - -# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag -# controls whether a binary table of contents is generated (YES) or a -# normal table of contents (NO) in the .chm file. - -BINARY_TOC = NO - -# The TOC_EXPAND flag can be set to YES to add extra items for group members -# to the contents of the HTML help documentation and to the tree view. - -TOC_EXPAND = NO - -# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and -# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated -# that can be used as input for Qt's qhelpgenerator to generate a -# Qt Compressed Help (.qch) of the generated HTML documentation. - -GENERATE_QHP = NO - -# If the QHG_LOCATION tag is specified, the QCH_FILE tag can -# be used to specify the file name of the resulting .qch file. -# The path specified is relative to the HTML output folder. - -QCH_FILE = - -# The QHP_NAMESPACE tag specifies the namespace to use when generating -# Qt Help Project output. For more information please see -# http://doc.trolltech.com/qthelpproject.html#namespace - -QHP_NAMESPACE = org.doxygen.Project - -# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating -# Qt Help Project output. For more information please see -# http://doc.trolltech.com/qthelpproject.html#virtual-folders - -QHP_VIRTUAL_FOLDER = doc - -# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to -# add. For more information please see -# http://doc.trolltech.com/qthelpproject.html#custom-filters - -QHP_CUST_FILTER_NAME = - -# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the -# custom filter to add. For more information please see -# -# Qt Help Project / Custom Filters. - -QHP_CUST_FILTER_ATTRS = - -# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this -# project's -# filter section matches. -# -# Qt Help Project / Filter Attributes. - -QHP_SECT_FILTER_ATTRS = - -# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can -# be used to specify the location of Qt's qhelpgenerator. -# If non-empty doxygen will try to run qhelpgenerator on the generated -# .qhp file. - -QHG_LOCATION = - -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files -# will be generated, which together with the HTML files, form an Eclipse help -# plugin. To install this plugin and make it available under the help contents -# menu in Eclipse, the contents of the directory containing the HTML and XML -# files needs to be copied into the plugins directory of eclipse. The name of -# the directory within the plugins directory should be the same as -# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before -# the help appears. - -GENERATE_ECLIPSEHELP = NO - -# A unique identifier for the eclipse help plugin. When installing the plugin -# the directory name containing the HTML and XML files should also have -# this name. - -ECLIPSE_DOC_ID = org.doxygen.Project - -# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) -# at top of each HTML page. The value NO (the default) enables the index and -# the value YES disables it. Since the tabs have the same information as the -# navigation tree you can set this option to NO if you already set -# GENERATE_TREEVIEW to YES. - -DISABLE_INDEX = NO - -# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index -# structure should be generated to display hierarchical information. -# If the tag value is set to YES, a side panel will be generated -# containing a tree-like index structure (just like the one that -# is generated for HTML Help). For this to work a browser that supports -# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). -# Windows users are probably better off using the HTML help feature. -# Since the tree basically has the same information as the tab index you -# could consider to set DISABLE_INDEX to NO when enabling this option. - -GENERATE_TREEVIEW = NO - -# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values -# (range [0,1..20]) that doxygen will group on one line in the generated HTML -# documentation. Note that a value of 0 will completely suppress the enum -# values from appearing in the overview section. - -ENUM_VALUES_PER_LINE = 4 - -# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, -# and Class Hierarchy pages using a tree view instead of an ordered list. - -USE_INLINE_TREES = NO - -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be -# used to set the initial width (in pixels) of the frame in which the tree -# is shown. - -TREEVIEW_WIDTH = 250 - -# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open -# links to external symbols imported via tag files in a separate window. - -EXT_LINKS_IN_WINDOW = NO - -# Use this tag to change the font size of Latex formulas included -# as images in the HTML documentation. The default is 10. Note that -# when you change the font size after a successful doxygen run you need -# to manually remove any form_*.png images from the HTML output directory -# to force them to be regenerated. - -FORMULA_FONTSIZE = 10 - -# Use the FORMULA_TRANPARENT tag to determine whether or not the images -# generated for formulas are transparent PNGs. Transparent PNGs are -# not supported properly for IE 6.0, but are supported on all modern browsers. -# Note that when changing this option you need to delete any form_*.png files -# in the HTML output before the changes have effect. - -FORMULA_TRANSPARENT = YES - -# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax -# (see http://www.mathjax.org) which uses client side Javascript for the -# rendering instead of using prerendered bitmaps. Use this if you do not -# have LaTeX installed or if you want to formulas look prettier in the HTML -# output. When enabled you may also need to install MathJax separately and -# configure the path to it using the MATHJAX_RELPATH option. - -USE_MATHJAX = NO - -# When MathJax is enabled you need to specify the location relative to the -# HTML output directory using the MATHJAX_RELPATH option. The destination -# directory should contain the MathJax.js script. For instance, if the mathjax -# directory is located at the same level as the HTML output directory, then -# MATHJAX_RELPATH should be ../mathjax. The default value points to -# the MathJax Content Delivery Network so you can quickly see the result without -# installing MathJax. -# However, it is strongly recommended to install a local -# copy of MathJax from http://www.mathjax.org before deployment. - -MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest - -# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension -# names that should be enabled during MathJax rendering. - -MATHJAX_EXTENSIONS = - -# When the SEARCHENGINE tag is enabled doxygen will generate a search box -# for the HTML output. The underlying search engine uses javascript -# and DHTML and should work on any modern browser. Note that when using -# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets -# (GENERATE_DOCSET) there is already a search function so this one should -# typically be disabled. For large projects the javascript based search engine -# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. - -SEARCHENGINE = YES - -# When the SERVER_BASED_SEARCH tag is enabled the search engine will be -# implemented using a PHP enabled web server instead of at the web client -# using Javascript. Doxygen will generate the search PHP script and index -# file to put on the web server. The advantage of the server -# based approach is that it scales better to large projects and allows -# full text search. The disadvantages are that it is more difficult to setup -# and does not have live searching capabilities. - -SERVER_BASED_SEARCH = NO - -#--------------------------------------------------------------------------- -# configuration options related to the LaTeX output -#--------------------------------------------------------------------------- - -# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will -# generate Latex output. - -GENERATE_LATEX = NO - -# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `latex' will be used as the default path. - -LATEX_OUTPUT = latex - -# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be -# invoked. If left blank `latex' will be used as the default command name. -# Note that when enabling USE_PDFLATEX this option is only used for -# generating bitmaps for formulas in the HTML output, but not in the -# Makefile that is written to the output directory. - -LATEX_CMD_NAME = latex - -# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to -# generate index for LaTeX. If left blank `makeindex' will be used as the -# default command name. - -MAKEINDEX_CMD_NAME = makeindex - -# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact -# LaTeX documents. This may be useful for small projects and may help to -# save some trees in general. - -COMPACT_LATEX = NO - -# The PAPER_TYPE tag can be used to set the paper type that is used -# by the printer. Possible values are: a4, letter, legal and -# executive. If left blank a4wide will be used. - -PAPER_TYPE = a4 - -# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX -# packages that should be included in the LaTeX output. - -EXTRA_PACKAGES = - -# The LATEX_HEADER tag can be used to specify a personal LaTeX header for -# the generated latex document. The header should contain everything until -# the first chapter. If it is left blank doxygen will generate a -# standard header. Notice: only use this tag if you know what you are doing! - -LATEX_HEADER = - -# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for -# the generated latex document. The footer should contain everything after -# the last chapter. If it is left blank doxygen will generate a -# standard footer. Notice: only use this tag if you know what you are doing! - -LATEX_FOOTER = - -# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated -# is prepared for conversion to pdf (using ps2pdf). The pdf file will -# contain links (just like the HTML output) instead of page references -# This makes the output suitable for online browsing using a pdf viewer. - -PDF_HYPERLINKS = YES - -# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of -# plain latex in the generated Makefile. Set this option to YES to get a -# higher quality PDF documentation. - -USE_PDFLATEX = YES - -# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. -# command to the generated LaTeX files. This will instruct LaTeX to keep -# running if errors occur, instead of asking the user for help. -# This option is also used when generating formulas in HTML. - -LATEX_BATCHMODE = NO - -# If LATEX_HIDE_INDICES is set to YES then doxygen will not -# include the index chapters (such as File Index, Compound Index, etc.) -# in the output. - -LATEX_HIDE_INDICES = NO - -# If LATEX_SOURCE_CODE is set to YES then doxygen will include -# source code with syntax highlighting in the LaTeX output. -# Note that which sources are shown also depends on other settings -# such as SOURCE_BROWSER. - -LATEX_SOURCE_CODE = NO - -# The LATEX_BIB_STYLE tag can be used to specify the style to use for the -# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See -# http://en.wikipedia.org/wiki/BibTeX for more info. - -LATEX_BIB_STYLE = plain - -#--------------------------------------------------------------------------- -# configuration options related to the RTF output -#--------------------------------------------------------------------------- - -# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output -# The RTF output is optimized for Word 97 and may not look very pretty with -# other RTF readers or editors. - -GENERATE_RTF = NO - -# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `rtf' will be used as the default path. - -RTF_OUTPUT = rtf - -# If the COMPACT_RTF tag is set to YES Doxygen generates more compact -# RTF documents. This may be useful for small projects and may help to -# save some trees in general. - -COMPACT_RTF = NO - -# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated -# will contain hyperlink fields. The RTF file will -# contain links (just like the HTML output) instead of page references. -# This makes the output suitable for online browsing using WORD or other -# programs which support those fields. -# Note: wordpad (write) and others do not support links. - -RTF_HYPERLINKS = NO - -# Load style sheet definitions from file. Syntax is similar to doxygen's -# config file, i.e. a series of assignments. You only have to provide -# replacements, missing definitions are set to their default value. - -RTF_STYLESHEET_FILE = - -# Set optional variables used in the generation of an rtf document. -# Syntax is similar to doxygen's config file. - -RTF_EXTENSIONS_FILE = - -#--------------------------------------------------------------------------- -# configuration options related to the man page output -#--------------------------------------------------------------------------- - -# If the GENERATE_MAN tag is set to YES (the default) Doxygen will -# generate man pages - -GENERATE_MAN = NO - -# The MAN_OUTPUT tag is used to specify where the man pages will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `man' will be used as the default path. - -MAN_OUTPUT = man - -# The MAN_EXTENSION tag determines the extension that is added to -# the generated man pages (default is the subroutine's section .3) - -MAN_EXTENSION = .3 - -# If the MAN_LINKS tag is set to YES and Doxygen generates man output, -# then it will generate one additional man file for each entity -# documented in the real man page(s). These additional files -# only source the real man page, but without them the man command -# would be unable to find the correct page. The default is NO. - -MAN_LINKS = NO - -#--------------------------------------------------------------------------- -# configuration options related to the XML output -#--------------------------------------------------------------------------- - -# If the GENERATE_XML tag is set to YES Doxygen will -# generate an XML file that captures the structure of -# the code including all documentation. - -GENERATE_XML = NO - -# The XML_OUTPUT tag is used to specify where the XML pages will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be -# put in front of it. If left blank `xml' will be used as the default path. - -XML_OUTPUT = xml - -# The XML_SCHEMA tag can be used to specify an XML schema, -# which can be used by a validating XML parser to check the -# syntax of the XML files. - -XML_SCHEMA = - -# The XML_DTD tag can be used to specify an XML DTD, -# which can be used by a validating XML parser to check the -# syntax of the XML files. - -XML_DTD = - -# If the XML_PROGRAMLISTING tag is set to YES Doxygen will -# dump the program listings (including syntax highlighting -# and cross-referencing information) to the XML output. Note that -# enabling this will significantly increase the size of the XML output. - -XML_PROGRAMLISTING = YES - -#--------------------------------------------------------------------------- -# configuration options for the AutoGen Definitions output -#--------------------------------------------------------------------------- - -# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will -# generate an AutoGen Definitions (see autogen.sf.net) file -# that captures the structure of the code including all -# documentation. Note that this feature is still experimental -# and incomplete at the moment. - -GENERATE_AUTOGEN_DEF = NO - -#--------------------------------------------------------------------------- -# configuration options related to the Perl module output -#--------------------------------------------------------------------------- - -# If the GENERATE_PERLMOD tag is set to YES Doxygen will -# generate a Perl module file that captures the structure of -# the code including all documentation. Note that this -# feature is still experimental and incomplete at the -# moment. - -GENERATE_PERLMOD = NO - -# If the PERLMOD_LATEX tag is set to YES Doxygen will generate -# the necessary Makefile rules, Perl scripts and LaTeX code to be able -# to generate PDF and DVI output from the Perl module output. - -PERLMOD_LATEX = NO - -# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be -# nicely formatted so it can be parsed by a human reader. -# This is useful -# if you want to understand what is going on. -# On the other hand, if this -# tag is set to NO the size of the Perl module output will be much smaller -# and Perl will parse it just the same. - -PERLMOD_PRETTY = YES - -# The names of the make variables in the generated doxyrules.make file -# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. -# This is useful so different doxyrules.make files included by the same -# Makefile don't overwrite each other's variables. - -PERLMOD_MAKEVAR_PREFIX = - -#--------------------------------------------------------------------------- -# Configuration options related to the preprocessor -#--------------------------------------------------------------------------- - -# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will -# evaluate all C-preprocessor directives found in the sources and include -# files. - -ENABLE_PREPROCESSING = YES - -# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro -# names in the source code. If set to NO (the default) only conditional -# compilation will be performed. Macro expansion can be done in a controlled -# way by setting EXPAND_ONLY_PREDEF to YES. - -MACRO_EXPANSION = NO - -# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES -# then the macro expansion is limited to the macros specified with the -# PREDEFINED and EXPAND_AS_DEFINED tags. - -EXPAND_ONLY_PREDEF = NO - -# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files -# pointed to by INCLUDE_PATH will be searched when a #include is found. - -SEARCH_INCLUDES = YES - -# The INCLUDE_PATH tag can be used to specify one or more directories that -# contain include files that are not input files but should be processed by -# the preprocessor. - -INCLUDE_PATH = - -# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard -# patterns (like *.h and *.hpp) to filter out the header-files in the -# directories. If left blank, the patterns specified with FILE_PATTERNS will -# be used. - -INCLUDE_FILE_PATTERNS = - -# The PREDEFINED tag can be used to specify one or more macro names that -# are defined before the preprocessor is started (similar to the -D option of -# gcc). The argument of the tag is a list of macros of the form: name -# or name=definition (no spaces). If the definition and the = are -# omitted =1 is assumed. To prevent a macro definition from being -# undefined via #undef or recursively expanded use the := operator -# instead of the = operator. - -PREDEFINED = - -# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then -# this tag can be used to specify a list of macro names that should be expanded. -# The macro definition that is found in the sources will be used. -# Use the PREDEFINED tag if you want to use a different macro definition that -# overrules the definition found in the source code. - -EXPAND_AS_DEFINED = - -# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then -# doxygen's preprocessor will remove all references to function-like macros -# that are alone on a line, have an all uppercase name, and do not end with a -# semicolon, because these will confuse the parser if not removed. - -SKIP_FUNCTION_MACROS = YES - -#--------------------------------------------------------------------------- -# Configuration::additions related to external references -#--------------------------------------------------------------------------- - -# The TAGFILES option can be used to specify one or more tagfiles. For each -# tag file the location of the external documentation should be added. The -# format of a tag file without this location is as follows: -# -# TAGFILES = file1 file2 ... -# Adding location for the tag files is done as follows: -# -# TAGFILES = file1=loc1 "file2 = loc2" ... -# where "loc1" and "loc2" can be relative or absolute paths -# or URLs. Note that each tag file must have a unique name (where the name does -# NOT include the path). If a tag file is not located in the directory in which -# doxygen is run, you must also specify the path to the tagfile here. - -TAGFILES = - -# When a file name is specified after GENERATE_TAGFILE, doxygen will create -# a tag file that is based on the input files it reads. - -GENERATE_TAGFILE = - -# If the ALLEXTERNALS tag is set to YES all external classes will be listed -# in the class index. If set to NO only the inherited external classes -# will be listed. - -ALLEXTERNALS = NO - -# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed -# in the modules index. If set to NO, only the current project's groups will -# be listed. - -EXTERNAL_GROUPS = YES - -# The PERL_PATH should be the absolute path and name of the perl script -# interpreter (i.e. the result of `which perl'). - -PERL_PATH = /usr/bin/perl - -#--------------------------------------------------------------------------- -# Configuration options related to the dot tool -#--------------------------------------------------------------------------- - -# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will -# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base -# or super classes. Setting the tag to NO turns the diagrams off. Note that -# this option also works with HAVE_DOT disabled, but it is recommended to -# install and use dot, since it yields more powerful graphs. - -CLASS_DIAGRAMS = YES - -# You can define message sequence charts within doxygen comments using the \msc -# command. Doxygen will then run the mscgen tool (see -# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the -# documentation. The MSCGEN_PATH tag allows you to specify the directory where -# the mscgen tool resides. If left empty the tool is assumed to be found in the -# default search path. - -MSCGEN_PATH = - -# If set to YES, the inheritance and collaboration graphs will hide -# inheritance and usage relations if the target is undocumented -# or is not a class. - -HIDE_UNDOC_RELATIONS = YES - -# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is -# available from the path. This tool is part of Graphviz, a graph visualization -# toolkit from AT&T and Lucent Bell Labs. The other options in this section -# have no effect if this option is set to NO (the default) - -HAVE_DOT = NO - -# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is -# allowed to run in parallel. When set to 0 (the default) doxygen will -# base this on the number of processors available in the system. You can set it -# explicitly to a value larger than 0 to get control over the balance -# between CPU load and processing speed. - -DOT_NUM_THREADS = 0 - -# By default doxygen will use the Helvetica font for all dot files that -# doxygen generates. When you want a differently looking font you can specify -# the font name using DOT_FONTNAME. You need to make sure dot is able to find -# the font, which can be done by putting it in a standard location or by setting -# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the -# directory containing the font. - -DOT_FONTNAME = Helvetica - -# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. -# The default size is 10pt. - -DOT_FONTSIZE = 10 - -# By default doxygen will tell dot to use the Helvetica font. -# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to -# set the path where dot can find it. - -DOT_FONTPATH = - -# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for each documented class showing the direct and -# indirect inheritance relations. Setting this tag to YES will force the -# CLASS_DIAGRAMS tag to NO. - -CLASS_GRAPH = YES - -# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for each documented class showing the direct and -# indirect implementation dependencies (inheritance, containment, and -# class references variables) of the class with other documented classes. - -COLLABORATION_GRAPH = YES - -# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen -# will generate a graph for groups, showing the direct groups dependencies - -GROUP_GRAPHS = YES - -# If the UML_LOOK tag is set to YES doxygen will generate inheritance and -# collaboration diagrams in a style similar to the OMG's Unified Modeling -# Language. - -UML_LOOK = NO - -# If the UML_LOOK tag is enabled, the fields and methods are shown inside -# the class node. If there are many fields or methods and many nodes the -# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS -# threshold limits the number of items for each type to make the size more -# managable. Set this to 0 for no limit. Note that the threshold may be -# exceeded by 50% before the limit is enforced. - -UML_LIMIT_NUM_FIELDS = 10 - -# If set to YES, the inheritance and collaboration graphs will show the -# relations between templates and their instances. - -TEMPLATE_RELATIONS = NO - -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT -# tags are set to YES then doxygen will generate a graph for each documented -# file showing the direct and indirect include dependencies of the file with -# other documented files. - -INCLUDE_GRAPH = YES - -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and -# HAVE_DOT tags are set to YES then doxygen will generate a graph for each -# documented header file showing the documented files that directly or -# indirectly include this file. - -INCLUDED_BY_GRAPH = YES - -# If the CALL_GRAPH and HAVE_DOT options are set to YES then -# doxygen will generate a call dependency graph for every global function -# or class method. Note that enabling this option will significantly increase -# the time of a run. So in most cases it will be better to enable call graphs -# for selected functions only using the \callgraph command. - -CALL_GRAPH = NO - -# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then -# doxygen will generate a caller dependency graph for every global function -# or class method. Note that enabling this option will significantly increase -# the time of a run. So in most cases it will be better to enable caller -# graphs for selected functions only using the \callergraph command. - -CALLER_GRAPH = NO - -# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen -# will generate a graphical hierarchy of all classes instead of a textual one. - -GRAPHICAL_HIERARCHY = YES - -# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES -# then doxygen will show the dependencies a directory has on other directories -# in a graphical way. The dependency relations are determined by the #include -# relations between the files in the directories. - -DIRECTORY_GRAPH = YES - -# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images -# generated by dot. Possible values are svg, png, jpg, or gif. -# If left blank png will be used. If you choose svg you need to set -# HTML_FILE_EXTENSION to xhtml in order to make the SVG files -# visible in IE 9+ (other browsers do not have this requirement). - -DOT_IMAGE_FORMAT = png - -# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to -# enable generation of interactive SVG images that allow zooming and panning. -# Note that this requires a modern browser other than Internet Explorer. -# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you -# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files -# visible. Older versions of IE do not have SVG support. - -INTERACTIVE_SVG = NO - -# The tag DOT_PATH can be used to specify the path where the dot tool can be -# found. If left blank, it is assumed the dot tool can be found in the path. - -DOT_PATH = - -# The DOTFILE_DIRS tag can be used to specify one or more directories that -# contain dot files that are included in the documentation (see the -# \dotfile command). - -DOTFILE_DIRS = - -# The MSCFILE_DIRS tag can be used to specify one or more directories that -# contain msc files that are included in the documentation (see the -# \mscfile command). - -MSCFILE_DIRS = - -# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of -# nodes that will be shown in the graph. If the number of nodes in a graph -# becomes larger than this value, doxygen will truncate the graph, which is -# visualized by representing a node as a red box. Note that doxygen if the -# number of direct children of the root node in a graph is already larger than -# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note -# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. - -DOT_GRAPH_MAX_NODES = 50 - -# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the -# graphs generated by dot. A depth value of 3 means that only nodes reachable -# from the root by following a path via at most 3 edges will be shown. Nodes -# that lay further from the root node will be omitted. Note that setting this -# option to 1 or 2 may greatly reduce the computation time needed for large -# code bases. Also note that the size of a graph can be further restricted by -# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. - -MAX_DOT_GRAPH_DEPTH = 0 - -# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent -# background. This is disabled by default, because dot on Windows does not -# seem to support this out of the box. Warning: Depending on the platform used, -# enabling this option may lead to badly anti-aliased labels on the edges of -# a graph (i.e. they become hard to read). - -DOT_TRANSPARENT = NO - -# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output -# files in one run (i.e. multiple -o and -T options on the command line). This -# makes dot run faster, but since only newer versions of dot (>1.8.10) -# support this, this feature is disabled by default. - -DOT_MULTI_TARGETS = NO - -# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will -# generate a legend page explaining the meaning of the various boxes and -# arrows in the dot generated graphs. - -GENERATE_LEGEND = YES - -# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will -# remove the intermediate dot files that are used to generate -# the various graphs. - -DOT_CLEANUP = YES diff --git a/plugins/MissingStars/resources/MissingStars.qrc b/plugins/MissingStars/resources/MissingStars.qrc deleted file mode 100644 index e876e467d6c77..0000000000000 --- a/plugins/MissingStars/resources/MissingStars.qrc +++ /dev/null @@ -1,5 +0,0 @@ - - - missingstars.json - - diff --git a/plugins/MissingStars/resources/missingstars.json b/plugins/MissingStars/resources/missingstars.json deleted file mode 100644 index 889a7dec5569e..0000000000000 --- a/plugins/MissingStars/resources/missingstars.json +++ /dev/null @@ -1,728 +0,0 @@ -{ - "shortName": "Missing stars data", - "catalog": - { - "η Car": - { - "RA": "10h45m03.545808s", - "DEC": "-59d41m03.95124s", - "pmRA": -11.0, - "pmDEC": 4.1, - "bMag": 7.03, - "vMag": 6.48, - "SpType": "LBV" - }, - "TYC 1309-1609-1": - { - "RA": "05h35m04.9551206928s", - "DEC": "+22d09m26.060109732s", - "pmRA": 1.595, - "pmDEC": -1.389, - "bMag": 11.5, - "vMag": 11.3, - "parallax": 0.3988, - "parallaxErr": 0.0214 - }, - "σ Ori C": - { - "RA": "05h38m44.1189397296s", - "DEC": "-02d36m06.310060884s", - "pmRA": 0.358, - "pmDEC": -1.064, - "bMag": 8.77, - "vMag": 8.79, - "parallax": 2.472, - "parallaxErr": 0.0293, - "SpType": "A2Vn" - }, - "Gaia DR2 3030024282585867776": - { - "RA": "07h37m35.8098876720s", - "DEC": "-14d25m07.649566608s", - "pmRA": 5.942, - "pmDEC": 5.275, - "bMag": 13.273, - "vMag": 12.634, - "parallax": 1.317, - "parallaxErr": 0.0126 - }, - "α CMa B": - { - "RA": "06h45m09.3041925037s", - "DEC": "-16d43m00.724740067s", - "pmRA": -461.571, - "pmDEC": -914.520, - "bMag": 8.41, - "vMag": 8.44, - "parallax": 374.4896, - "parallaxErr": 0.2313, - "SpType": "DA1.9" - }, - "α CMi B": - { - "RA": "07h39m17.8800s", - "DEC": "+05d13m26.800s", - "pmRA": -709.0, - "pmDEC": -1024.0, - "bMag": 10.7, - "vMag": 10.92, - "SpType": "DQZ" - }, - "V1326 Ori": - { - "RA": "05h35m09.7681644000s", - "DEC": "-05d23m26.898475704s", - "pmRA": 1.200, - "pmDEC": 0.523, - "bMag": 14.776, - "vMag": 13.806, - "parallax": 2.5468, - "parallaxErr": 0.038, - "SpType": "K8" - }, - "V1327 Ori A": - { - "RA": "05h35m10.4918753664s", - "DEC": "-05d22m45.681747240s", - "pmRA": 2.263, - "pmDEC": -2.396, - "bMag": 15.896, - "vMag": 14.820, - "parallax": 2.2938, - "parallaxErr": 0.1014, - "SpType": "M0.5" - }, - "LQ Ori": - { - "RA": "05h35m10.7315904000s", - "DEC": "-05d23m44.694430944s", - "pmRA": 1.996, - "pmDEC": 0.740, - "bMag": 13.527, - "vMag": 12.455, - "parallax": 2.9824, - "parallaxErr": 0.0646, - "SpType": "K8" - }, - "V1228 Ori": - { - "RA": "05h35m12.2788891920s", - "DEC": "-05d23m48.027111936s", - "pmRA": 1.969, - "pmDEC": -0.001, - "bMag": 15.361, - "vMag": 14.238, - "parallax": 2.0507, - "parallaxErr": 0.326, - "SpType": "K1" - }, - "LV Ori": - { - "RA": "05h35m12.5989281816s", - "DEC": "-05d23m44.110995828s", - "pmRA": 2.436, - "pmDEC": -1.289, - "bMag": 13.863, - "vMag": 12.912, - "parallax": 2.5983, - "parallaxErr": 0.0205, - "SpType": "K1V" - }, - "V2228 Ori": - { - "RA": "05h35m12.8166620400s", - "DEC": "-05d20m43.608349428s", - "pmRA": 0.512, - "pmDEC": 1.031, - "bMag": 16.413, - "vMag": 15.458, - "parallax": 2.7278, - "parallaxErr": 0.1535, - "SpType": "M1e" - }, - "V1398 Ori": - { - "RA": "05h35m13.4462334000s", - "DEC": "-05d23m40.264692468s", - "pmRA": 1.263, - "pmDEC": -0.700, - "bMag": 15.790, - "vMag": 14.937, - "parallax": 1.9904, - "parallaxErr": 0.3274, - "SpType": "M0" - }, - "V1496 Ori": - { - "RA": "05h35m13.7999053320s", - "DEC": "-05d22m07.022740116s", - "pmRA": 0.141, - "pmDEC": -0.354, - "bMag": 16.184, - "vMag": 14.987, - "parallax": 2.4839, - "parallaxErr": 0.0388, - "SpType": "K2e" - }, - "V1328 Ori": - { - "RA": "05h35m14.2769307624s", - "DEC": "-05d24m24.668694324s", - "pmRA": 1.260, - "pmDEC": -0.519, - "bMag": 15.025, - "vMag": 13.988, - "parallax": 2.5825, - "parallaxErr": 0.0554, - "SpType": "K7" - }, - "V1330 Ori": - { - "RA": "05h35m14.9155657944s", - "DEC": "-05d22m39.203240880s", - "pmRA": 1.925, - "pmDEC": -0.392, - "bMag": 15.040, - "vMag": 13.940, - "parallax": 2.3346, - "parallaxErr": 0.0534, - "SpType": "K4" - }, - "V1278 Ori": - { - "RA": "05h35m15.2038151952s", - "DEC": "-05d22m24.062782908s", - "pmRA": 0.408, - "pmDEC": 0.160, - "bMag": 16.124, - "vMag": 15.222, - "parallax": 2.5469, - "parallaxErr": 0.0429, - "SpType": "K7" - }, - "V1501 Ori": - { - "RA": "05h35m15.5533377312s", - "DEC": "-05d25m14.147311764s", - "pmRA": 1.532, - "pmDEC": 1.374, - "bMag": 15.163, - "vMag": 14.077, - "parallax": 2.5051, - "parallaxErr": 0.0506, - "SpType": "K4-M1" - }, - "V348 Ori": - { - "RA": "05h35m15.6352887504s", - "DEC": "-05d22m56.458393068s", - "pmRA": 1.107, - "pmDEC": 1.524, - "bMag": 14.352, - "vMag": 13.274, - "parallax": 2.5113, - "parallaxErr": 0.0263, - "SpType": "G8-K1" - }, - "V2279 Ori": - { - "RA": "05h35m15.9506536656s", - "DEC": "-05d23m49.996939416s", - "pmRA": 0.517, - "pmDEC": -1.881, - "bMag": 13.648, - "vMag": 12.730, - "parallax": 2.2167, - "parallaxErr": 0.205, - "SpType": "M0.5+M2" - }, - "AC Ori": - { - "RA": "05h35m16.0009377816s", - "DEC": "-05d23m52.972404288s", - "pmRA": 2.878, - "pmDEC": -0.975, - "vMag": 14.875, - "parallax": 2.3154, - "parallaxErr": 0.0599, - "SpType": "F5e" - }, - "V2280 Ori": - { - "RA": "05h35m16.0670493984s", - "DEC": "-05d20m36.296868192s", - "pmRA": 2.143, - "pmDEC": 3.834, - "bMag": 16.287, - "vMag": 15.177, - "parallax": 2.8809, - "parallaxErr": 0.1644 - }, - "V1279 Ori": - { - "RA": "05h35m16.7666721456s", - "DEC": "-05d24m04.257205308s", - "pmRA": 0.137, - "pmDEC": 1.010, - "bMag": 14.815, - "vMag": 13.722, - "parallax": 1.7408, - "parallaxErr": 0.1351, - "SpType": "M0.9e" - }, - "MR Ori": - { - "RA": "05h35m16.9783073496s", - "DEC": "-05d21m45.337307544s", - "pmRA": 0.851, - "pmDEC": 1.601, - "bMag": 10.876, - "vMag": 10.578, - "parallax": 2.5044, - "parallaxErr": 0.0162, - "SpType": "A2:Vv" - }, - "V1333 Ori": - { - "RA": "05h35m17.0062131816s", - "DEC": "-05d22m33.026587572s", - "pmRA": 1.703, - "pmDEC": 0.955, - "bMag": 15.634, - "vMag": 14.509, - "parallax": 2.5025, - "parallaxErr": 0.0335, - "SpType": "K0-K2" - }, - "V2299 Ori": - { - "RA": "05h35m17.0669790936s", - "DEC": "-05d23m34.044628704s", - "pmRA": 0.733, - "pmDEC": 0.958, - "bMag": 14.224, - "vMag": 13.322, - "parallax": 1.9105, - "parallaxErr": 0.0654, - "SpType": "K1" - }, - "HD 37024": - { - "RA": "05h35m17.3524325856s", - "DEC": "-05d22m35.734959444s", - "pmRA": 0.872, - "pmDEC": 0.334, - "vMag": 16.29, - "parallax": 3.0812, - "parallaxErr": 0.196, - "SpType": "K0.7" - }, - "V1510 Ori": - { - "RA": "05h35m17.5584374544s", - "DEC": "-05d22m56.774010216s", - "pmRA": 3.720, - "pmDEC": -0.291, - "bMag": 15.991, - "vMag": 15.003, - "parallax": 4.7036, - "parallaxErr": 0.3581, - "SpType": "K7+M1" - }, - "V2314 Ori A": - { - "RA": "05h35m17.8466478048s", - "DEC": "-05d20m54.049764660s", - "pmRA": 1.367, - "pmDEC": 1.437, - "bMag": 16.539, - "vMag": 15.391, - "parallax": 2.565, - "parallaxErr": 0.0399 - }, - "MT Ori": - { - "RA": "05h35m17.9482748184s", - "DEC": "-05d22m45.477710148s", - "pmRA": 3.971, - "pmDEC": 2.744, - "bMag": 13.208, - "vMag": 12.229, - "parallax": 2.4841, - "parallaxErr": 0.041, - "SpType": "K2" - }, - "V2325 Ori": - { - "RA": "05h35m18.2064680088s", - "DEC": "-05d23m35.904973236s", - "pmRA": 1.570, - "pmDEC": -0.033, - "bMag": 14.920, - "vMag": 13.923, - "parallax": 2.5327, - "parallaxErr": 0.0374, - "SpType": "M0" - }, - "V1229 Ori": - { - "RA": "05h35m18.3705735744s", - "DEC": "-05d22m37.440079608s", - "pmRA": 2.147, - "pmDEC": 0.783, - "bMag": 14.257, - "vMag": 13.251, - "parallax": 2.5695, - "parallaxErr": 0.0303, - "SpType": "K0" - }, - "MV Ori": - { - "RA": "05h35m18.6726304944s", - "DEC": "-05d20m33.720896364s", - "pmRA": 0.468, - "pmDEC": 0.399, - "bMag": 13.736, - "vMag": 12.725, - "parallax": 2.6253, - "parallaxErr": 0.1592, - "SpType": "G1e" - }, - "Brun 633": - { - "RA": "05h35m19.1394733464s", - "DEC": "-05d20m38.745465468s", - "pmRA": 0.126, - "pmDEC": 1.155, - "bMag": 12.971, - "vMag": 12.523, - "parallax": 2.5091, - "parallaxErr": 0.0188, - "SpType": "A4-A7" - }, - "V2356 Ori": - { - "RA": "05h35m19.6592535024s", - "DEC": "-05d24m26.602668792s", - "pmRA": 1.377, - "pmDEC": -0.997, - "vMag": 15.711, - "parallax": 2.5354, - "parallaxErr": 0.0495, - "SpType": "M1.2e" - }, - "V491 Ori": - { - "RA": "05h35m20.0525646096s", - "DEC": "-05d21m05.959872648s", - "pmRA": 0.131, - "pmDEC": 2.020, - "bMag": 16.647, - "vMag": 15.421, - "parallax": 2.2103, - "parallaxErr": 0.1598, - "SpType": "K7" - }, - "TU Ori": - { - "RA": "05h35m20.2232691384s", - "DEC": "-05d20m56.947917084s", - "pmRA": -1.214, - "pmDEC": -2.357, - "bMag": 13.736, - "vMag": 12.664, - "parallax": 3.982, - "parallaxErr": 0.7648, - "SpType": "G9" - }, - "V1520 Ori": - { - "RA": "05h35m20.45352s", - "DEC": "-05d23m29.7708s", - "bMag": 17.572, - "vMag": 15.912, - "SpType": "M0+M3.5" - }, - "V1230 Ori": - { - "RA": "05h35m20.7204225144s", - "DEC": "-05d21m44.345341872s", - "pmRA": 3.064, - "pmDEC": -1.425, - "bMag": 10.041, - "vMag": 9.736, - "parallax": 2.4554, - "parallaxErr": 0.031, - "SpType": "B1" - }, - "V1399 Ori": - { - "RA": "05h35m21.0488798160s", - "DEC": "-05d23m49.016892876s", - "pmRA": 0.437, - "pmDEC": 0.790, - "bMag": 13.231, - "vMag": 12.376, - "parallax": 2.5234, - "parallaxErr": 0.065, - "SpType": "G8" - }, - "V377 Ori": - { - "RA": "05h35m21.2917510440s", - "DEC": "-05d24m57.399203052s", - "pmRA": 2.270, - "pmDEC": 1.770, - "bMag": 14.995, - "vMag": 14.049, - "parallax": 2.5271, - "parallaxErr": 0.0309, - "SpType": "K1.5" - }, - "V494 Ori": - { - "RA": "05h35m21.8065385568s", - "DEC": "-05d23m53.893849416s", - "pmRA": 1.251, - "pmDEC": 1.480, - "bMag": 14.524, - "vMag": 13.485, - "parallax": 2.5865, - "parallaxErr": 0.0243, - "SpType": "M1" - }, - "V562 Ori": - { - "RA": "05h35m22.1895865176s", - "DEC": "-05d24m24.883699860s", - "pmRA": 1.440, - "pmDEC": 1.748, - "bMag": 15.389, - "vMag": 14.215, - "parallax": 2.5098, - "parallaxErr": 0.0363, - "SpType": "K2.5" - }, - "V1527 Ori": - { - "RA": "05h35m22.5471324720s", - "DEC": "-05d23m43.716322104s", - "pmRA": 1.879, - "pmDEC": 2.043, - "bMag": 16.607, - "vMag": 15.496, - "parallax": 2.5045, - "parallaxErr": 0.0398, - "SpType": "M0" - }, - "V2423 Ori": - { - "RA": "05h35m24.4375299696s", - "DEC": "-05d24m39.850507332s", - "pmRA": 2.248, - "pmDEC": -0.962, - "bMag": 15.834, - "vMag": 15.162, - "parallax": 2.4976, - "parallaxErr": 0.0586, - "SpType": "M0e" - }, - "V1400 Ori": - { - "RA": "05h35m24.6962195976s", - "DEC": "-05d24m35.734753224s", - "pmRA": 1.302, - "pmDEC": 1.910, - "bMag": 16.946, - "vMag": 15.847, - "parallax": 2.5475, - "parallaxErr": 0.0555, - "SpType": "M0e" - }, - "COUP 648": - { - "RA": "05h35m14.6556309840s", - "DEC": "-05d22m33.743501832s", - "pmRA": 1.084, - "pmDEC": -0.218, - "bMag": 15.891, - "vMag": 14.779, - "parallax": 2.2825, - "parallaxErr": 0.059, - "SpType": "K7" - }, - "COUP 672": - { - "RA": "05h35m14.9489989176s", - "DEC": "-05d23m39.225767352s", - "pmRA": 0.869, - "pmDEC": -0.361, - "bMag": 15.249, - "vMag": 14.247, - "parallax": 2.3188, - "parallaxErr": 0.0462 - }, - "COUP 742": - { - "RA": "05h35m15.8374571424s", - "DEC": "-05d22m45.841540404s", - "pmRA": 1.246, - "pmDEC": -2.360, - "vMag": 16.466, - "parallax": 2.681, - "parallaxErr": 0.0759, - "SpType": "M3e" - }, - "COUP 1100": - { - "RA": "05h35m20.3977430736s", - "DEC": "-05d22m13.636281216s", - "pmRA": 2.015, - "pmDEC": 0.490, - "bMag": 17.885, - "vMag": 16.618, - "parallax": 2.4294, - "parallaxErr": 0.064, - "SpType": "K" - }, - "θ2 Ori C": - { - "RA": "05h35m31.4311124640s", - "DEC": "-05d25m16.371705000s", - "pmRA": 2.510, - "pmDEC": 3.731, - "bMag": 7.80, - "vMag": 8.24, - "parallax": 2.4513, - "parallaxErr": 0.038, - "SpType": "B4V" - }, - "TYC 3592-7373-1": - { - "RA": "21h08m26.5460620176s", - "DEC": "+47d40m26.315990976s", - "pmRA": -4.004, - "pmDEC": -3.965, - "bMag": 10.9, - "vMag": 10.5, - "parallax": 0.3894, - "parallaxErr": 0.01, - "SpType": "B2V:npe" - }, - "HD 290572": - { - "RA": "05h33m54.5445906960s", - "DEC": "-00d06m21.223590696s", - "pmRA": -3.005, - "pmDEC": -4.471, - "bMag": 10.79, - "vMag": 10.48, - "parallax": 3.0109, - "parallaxErr": 0.0293, - "SpType": "F0" - }, - "HD 349999": - { - "RA": "19h25m19.9876564872s", - "DEC": "+20d14m14.352664884s", - "pmRA": 17.173, - "pmDEC": 27.930, - "bMag": 10.11, - "vMag": 9.67, - "parallax": 4.9001, - "parallaxErr": 0.0272, - "SpType": "F9" - }, - "HD 350001": - { - "RA": "19h24m41.2266182808s", - "DEC": "+19d47m13.030738008s", - "pmRA": -0.652, - "pmDEC": -5.409, - "bMag": 11.10, - "vMag": 9.93, - "parallax": 0.8578, - "parallaxErr": 0.0143, - "SpType": "A3II" - }, - "HD 350036": - { - "RA": "19h26m42.8627910240s", - "DEC": "+20d11m22.340693400s", - "pmRA": -73.375, - "pmDEC": -80.473, - "bMag": 11.0, - "vMag": 10.16, - "parallax": 13.743, - "parallaxErr": 0.0155, - "SpType": "K2" - }, - "HD 350037": - { - "RA": "19h26m48.6929604792s", - "DEC": "+20d09m58.775228208s", - "pmRA": -5.485, - "pmDEC": -44.177, - "bMag": 9.90, - "vMag": 9.24, - "parallax": 5.6619, - "parallaxErr": 0.0156, - "SpType": "G0" - }, - "Gaia DR3 4365631984908750336": - { - "RA": "16h55m58.5393377640s", - "DEC": "-04d06m35.657424252s", - "pmRA": -3.267, - "pmDEC": -4.753, - "bMag": 11.47, - "vMag": 9.68, - "parallax": 0.6219, - "parallaxErr": 0.0389 - }, - "Gaia DR3 4365625868875307648": - { - "RA": "16h56m01.1270029224s", - "DEC": "-04d13m40.643294196s", - "pmRA": -7.080, - "pmDEC": -1.349, - "bMag": 12.82, - "vMag": 11.40, - "parallax": 0.3035, - "parallaxErr": 0.0312 - }, - "Gaia DR3 4377545876286912896": - { - "RA": "16h55m05.4628980672s", - "DEC": "-04d10m58.570162644s", - "pmRA": -1.834, - "pmDEC": 5.842, - "bMag": 12.824, - "vMag": 11.691, - "parallax": 1.0502, - "parallaxErr": 0.0342 - }, - "Gaia DR3 4365535949433713024": - { - "RA": "16h55m11.1816127282s", - "DEC": "-04d12m57.210475528s", - "pmRA": -2.584, - "pmDEC": -0.167, - "bMag": 13.782, - "vMag": 12.537, - "parallax": 0.4785, - "parallaxErr": 0.0124 - }, - "Gaia DR3 4365534712483091840": - { - "RA": "16h55m30.9168274224s", - "DEC": "-04d15m40.735742184s", - "pmRA": 3.583, - "pmDEC": 6.215, - "bMag": 13.77, - "vMag": 13.07, - "parallax": 1.2638, - "parallaxErr": 0.0149 - } - } -} diff --git a/plugins/MissingStars/src/CMakeLists.txt b/plugins/MissingStars/src/CMakeLists.txt deleted file mode 100644 index 1c5e9fb30f212..0000000000000 --- a/plugins/MissingStars/src/CMakeLists.txt +++ /dev/null @@ -1,40 +0,0 @@ -INCLUDE_DIRECTORIES( - . - gui - ${CMAKE_BINARY_DIR}/plugins/MissingStars/src - ${CMAKE_BINARY_DIR}/plugins/MissingStars/src/gui -) - -LINK_DIRECTORIES(${CMAKE_BINARY_DIR}/src) - -SET(MissingStars_SRCS - MissingStars.hpp - MissingStars.cpp - MissingStar.hpp - MissingStar.cpp - gui/MissingStarsDialog.hpp - gui/MissingStarsDialog.cpp -) - -SET(MissingStarsDialog_UIS - gui/missingStarsDialog.ui -) - -SET(MissingStars_RES ../resources/MissingStars.qrc) -IF (${QT_VERSION_MAJOR} EQUAL "5") - QT5_WRAP_UI(MissingStarsDialog_UIS_H ${MissingStarsDialog_UIS}) - QT5_ADD_RESOURCES(MissingStars_RES_CXX ${MissingStars_RES}) -ELSE() - QT_WRAP_UI(MissingStarsDialog_UIS_H ${MissingStarsDialog_UIS}) - QT_ADD_RESOURCES(MissingStars_RES_CXX ${MissingStars_RES}) -ENDIF() - -ADD_LIBRARY(MissingStars-static STATIC ${MissingStars_SRCS} ${MissingStars_RES_CXX} ${MissingStarsDialog_UIS_H}) -TARGET_LINK_LIBRARIES(MissingStars-static Qt${QT_VERSION_MAJOR}::Core Qt${QT_VERSION_MAJOR}::Widgets) - -SET_TARGET_PROPERTIES(MissingStars-static PROPERTIES OUTPUT_NAME "MissingStars") -SET_TARGET_PROPERTIES(MissingStars-static PROPERTIES COMPILE_FLAGS "-DQT_STATICPLUGIN") -ADD_DEPENDENCIES(AllStaticPlugins MissingStars-static) - -SET_TARGET_PROPERTIES(MissingStars-static PROPERTIES FOLDER "plugins/MissingStars") - diff --git a/plugins/MissingStars/src/MissingStar.cpp b/plugins/MissingStars/src/MissingStar.cpp deleted file mode 100644 index 5b87abe2026ec..0000000000000 --- a/plugins/MissingStars/src/MissingStar.cpp +++ /dev/null @@ -1,260 +0,0 @@ -/* - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. - */ - -#include "MissingStar.hpp" -#include "StelObject.hpp" -#include "StelPainter.hpp" -#include "StelApp.hpp" -#include "StelCore.hpp" -#include "StelUtils.hpp" -#include "StelTranslator.hpp" -#include "StelModuleMgr.hpp" -#include "StelSkyDrawer.hpp" -#include "StelLocaleMgr.hpp" -#include "Planet.hpp" - -#include -#include -#include -#include -#include -#include - -const QString MissingStar::MISSINGSTAR_TYPE = QStringLiteral("MissingStar"); -bool MissingStar::flagShowLabels = true; - -MissingStar::MissingStar(const QVariantMap& map) - : initialized(false) - , designation("") - , RA(0.) - , DEC(0.) - , pmRA(0.f) - , pmDEC(0.f) - , bMag(-99.f) - , vMag(-99.f) - , parallax(0.f) - , parallaxErr(0.f) - , spType("") - , bvFlag(false) -{ - if (!map.contains("designation") || !map.contains("RA") || !map.contains("DEC") || !map.contains("vMag")) - { - qWarning() << "MissingStar: INVALID star!" << map.value("designation").toString(); - return; - } - - designation = map.value("designation").toString(); - RA = StelUtils::getDecAngle(map.value("RA").toString()); - DEC = StelUtils::getDecAngle(map.value("DEC").toString()); - pmRA = map.value("pmRA", 0.f).toFloat(); - pmDEC = map.value("pmDEC", 0.f).toFloat(); - bMag = map.value("bMag", -99.f).toFloat(); - vMag = map.value("vMag", -99.f).toFloat(); - parallax = map.value("parallax", 0.f).toFloat(); - parallaxErr = map.value("parallaxErr", 0.f).toFloat(); - spType = map.value("SpType", "").toString(); - - double b_v = 0.; - if (bMag>-99.f && vMag>-99.f) - { - b_v = (bMag-vMag)*1000.0; - if (b_v < -500.) { - b_v = -500.; - } else if (b_v > 3499.) { - b_v = 3499.; - } - bvFlag = true; - } - colorIndex = (unsigned int)floor(0.5+127.0*((500.0+b_v)/4000.0)); - - initialized = true; -} - -MissingStar::~MissingStar() -{ - // -} - -QVariantMap MissingStar::getMap(void) const -{ - const QVariantMap map = { - {"designation", designation}, - {"RA", RA}, - {"DEC", DEC}, - {"pmRA", pmRA}, - {"pmDEC", pmDEC}, - {"bMag", bMag}, - {"vMag", vMag}, - {"parallax", parallax}, - {"parallaxErr", parallaxErr}, - {"SpType", spType} - }; - - return map; -} - -QString MissingStar::getNameI18n(void) const -{ - return designation; -} - -QString MissingStar::getEnglishName(void) const -{ - return designation; -} - -QString MissingStar::getInfoString(const StelCore* core, const InfoStringGroup& flags) const -{ - QString str; - QTextStream oss(&str); - - if (flags&Name) - oss << "

" << getNameI18n() << "

"; - - if (flags&ObjectType) - oss << QString("%1: %2").arg(q_("Type"), getObjectTypeI18n()) << "
"; - - if (flags&Magnitude) - oss << getMagnitudeInfoString(core, flags, 2); - - if (flags&AbsoluteMagnitude) - { - if (parallax>0.f) - oss << QString("%1: %2").arg(q_("Absolute Magnitude")).arg(getVMagnitude(core)+5.*(1.+std::log10(0.001*parallax)), 0, 'f', 2) << "
"; - oss << getExtraInfoStrings(AbsoluteMagnitude).join(""); - } - - if (flags&Extra && bvFlag) - oss << QString("%1: %2").arg(q_("Color Index (B-V)"), QString::number(bMag-vMag, 'f', 2)) << "
"; - - // Ra/Dec etc. - oss << getCommonInfoString(core, flags); - - if (flags&Distance) - { - if (parallax>0.f) - { - //TRANSLATORS: Unit of measure for distance - Light Years - QString ly = qc_("ly", "distance"); - double k = AU/(SPEED_OF_LIGHT*86400*365.25); - double d = ((0.001/3600.)*(M_PI/180)); - double distance = k/(parallax*d); - if (parallaxErr>0.f && parallax>parallaxErr) // No distance when error of parallax is bigger than parallax! - oss << QString("%1: %2%3%4 %5").arg(q_("Distance"), QString::number(distance, 'f', 2), QChar(0x00B1), QString::number(qAbs(k/((parallaxErr + parallax)*d) - distance), 'f', 2), ly) << "
"; - else - oss << QString("%1: %2 %3").arg(q_("Distance"), QString::number(distance, 'f', 2), ly) << "
"; - } - oss << getExtraInfoStrings(Distance).join(""); - } - - if (flags&ProperMotion && (pmRA!=0.0 && pmDEC!=0.0)) - { - double pa = std::atan2(pmRA, pmDEC)*M_180_PI; - if (pa<0) - pa += 360.; - oss << QString("%1: %2 %3 %4 %5°
").arg(q_("Proper motion"), - QString::number(std::sqrt(pmRA*pmRA + pmDEC*pmDEC), 'f', 1), qc_("mas/yr", "milliarc second per year"), - qc_("towards", "into the direction of"), QString::number(pa, 'f', 1)); - oss << QString("%1: %2 %3 (%4)
").arg(q_("Proper motions by axes"), QString::number(pmRA, 'f', 1), QString::number(pmDEC, 'f', 1), qc_("mas/yr", "milliarc second per year")); - } - - if (flags&Extra) - { - if (parallax>0.f) - { - QString plx = q_("Parallax"); - if (parallaxErr>0.f) - oss << QString("%1: %2%3%4 ").arg(plx, QString::number(parallax, 'f', 3), QChar(0x00B1), QString::number(parallaxErr, 'f', 3)); - else - oss << QString("%1: %2 ").arg(plx, QString::number(parallax, 'f', 3)); - oss << qc_("mas", "parallax") << "
"; - } - - if (!spType.isEmpty()) - oss << QString("%1: %2").arg(q_("Spectral Type"), spType) << "
"; - } - - oss << getSolarLunarInfoString(core, flags); - postProcessInfoString(str, flags); - return str; -} - -float MissingStar::getVMagnitude(const StelCore* core) const -{ - Q_UNUSED(core) - return vMag; -} - -Vec3f MissingStar::getInfoColor(void) const -{ - return StelSkyDrawer::indexToColor(colorIndex); -} - -void MissingStar::draw(StelCore* core, StelPainter *painter) -{ - Vec3d pos = getJ2000EquatorialPos(core); - Vec3d win; - // Check visibility of missing star - if(!(painter->getProjector()->projectCheck(pos, win))) - return; - - StelSkyDrawer* sd = core->getSkyDrawer(); - const float mlimit = sd->getFlagStarMagnitudeLimit() ? sd->getCustomStarMagnitudeLimit() : sd->getLimitMagnitude(); - const float mag = getVMagnitudeWithExtinction(core); - const bool visibleStar = (mag <= mlimit); - const bool visibleHint = ((mag+5.f)j2000ToAltAzInPlaceNoRefraction(&altAz); - RCMag rcMag; - sd->computeRCMag(mag, &rcMag); - sd->preDrawPointSource(painter); - // allow height-dependent twinkle and suppress twinkling in higher altitudes. Keep 0.1 twinkle amount in zenith. - sd->drawPointSource(painter, pos, rcMag, color, true, qMin(1.0f, 1.0f-0.9f*static_cast(altAz[2]))); - sd->postDrawPointSource(painter); - painter->setColor(color, 1.f); - if (flagShowLabels && visibleHint) - painter->drawText(pos, designation, 0, shift, shift, false); - } -} - -Vec3d MissingStar::getJ2000EquatorialPos(const StelCore* core) const -{ - Vec3d v; - static const double d2000 = 2451545.0; - const double movementFactor = (M_PI/180.)*(0.0001/3600.) * (core->getJDE()-d2000)/365.25; - const double cRA = RA + movementFactor*pmRA/::cos(DEC*M_180_PI); - const double cDE = DEC + movementFactor*pmDEC; - StelUtils::spheToRect(cRA, cDE, v); - - if ((core) && (core->getUseAberration()) && (core->getCurrentPlanet())) - { - Vec3d vel=core->getCurrentPlanet()->getHeliocentricEclipticVelocity(); - vel=StelCore::matVsop87ToJ2000*vel*core->getAberrationFactor()*(AU/(86400.0*SPEED_OF_LIGHT)); - Vec3d pos=v+vel; - pos.normalize(); - return pos; - } - else - return v; -} diff --git a/plugins/MissingStars/src/MissingStar.hpp b/plugins/MissingStars/src/MissingStar.hpp deleted file mode 100644 index 7eae82d55459d..0000000000000 --- a/plugins/MissingStars/src/MissingStar.hpp +++ /dev/null @@ -1,120 +0,0 @@ -/* - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. - */ - -#ifndef MISSINGSTAR_HPP -#define MISSINGSTAR_HPP - -#include -#include -#include -#include -#include -#include - -#include "StelObject.hpp" -#include "StelTextureTypes.hpp" -#include "StelTranslator.hpp" - -class StelPainter; - -//! @class MissingStar -//! A Missing Star object represents one missing star on the sky. -//! Details about the missing stars are passed using a QVariant which contains -//! a map of data from the json file. -//! @ingroup missingStars - -class MissingStar : public StelObject -{ - friend class MissingStars; -public: - static const QString MISSINGSTAR_TYPE; - - //! @param map The data map for a missing star - MissingStar(const QVariantMap& map); - ~MissingStar() override; - - //! Get a QVariantMap which describes the missing star. Could be used to create a duplicate. - //! - designation - //! - RA (J2000.0) - //! - DEC (J2000.0) - //! - pmRA [mas/yr] - //! - pmDEC [mas/yr] - //! - bMag - //! - vMag - //! - parallax [mas] - //! - parallaxErr [mas] - //! - SpType - QVariantMap getMap(void) const; - - QString getType(void) const override - { - return MISSINGSTAR_TYPE; - } - - QString getObjectType(void) const override - { - return N_("star"); - } - QString getObjectTypeI18n(void) const override - { - return q_(getObjectType()); - } - - QString getID(void) const override - { - return designation; - } - - //! Get an HTML string to describe the object - //! @param core A pointer to the core - //! @flags a set of flags with information types to include. - QString getInfoString(const StelCore* core, const InfoStringGroup& flags) const override; - //! Return a map like StelObject::getInfoMap(), but with a few extra tags also available in getMap(). - //QVariantMap getInfoMap(const StelCore *core) const override; - Vec3f getInfoColor(void) const override; - Vec3d getJ2000EquatorialPos(const StelCore *core) const override; - float getVMagnitude(const StelCore* core) const override; - QString getNameI18n(void) const override; - QString getEnglishName(void) const override; - -private: - bool initialized; - - static StelTextureSP hintTexture; - - void draw(StelCore* core, StelPainter *painter); - - // Missing Star - QString designation; //! The ID of the missing star - double RA; //! R.A. (J2000.0) for the missing star - double DEC; //! Dec. (J2000.0) for the missing star - float pmRA; //! proper motion in R.A. for the missing star [mas/yr] - float pmDEC; //! proper motion in Dec. for the missing star [mas/yr] - float bMag; //! B magnitude for the missing star - float vMag; //! V magnitude for the missing star - float parallax; //! parallax for the missing star [mas] - float parallaxErr; //! parallax error for the missing star [mas] - QString spType; //! spectral type for the missing star - - int colorIndex; - bool bvFlag; - - static bool flagShowLabels; -}; - -#endif // MISSINGSTAR_HPP diff --git a/plugins/MissingStars/src/MissingStars.cpp b/plugins/MissingStars/src/MissingStars.cpp deleted file mode 100644 index c80e6a75d3704..0000000000000 --- a/plugins/MissingStars/src/MissingStars.cpp +++ /dev/null @@ -1,306 +0,0 @@ -/* - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. - */ - -#include "StelProjector.hpp" -#include "StelPainter.hpp" -#include "StelApp.hpp" -#include "StelCore.hpp" -#include "StelModuleMgr.hpp" -#include "StelObjectMgr.hpp" -#include "StelTextureMgr.hpp" -#include "StelJsonParser.hpp" -#include "StelFileMgr.hpp" -#include "StelTranslator.hpp" -#include "StarMgr.hpp" -#include "MissingStar.hpp" -#include "MissingStars.hpp" -#include "MissingStarsDialog.hpp" - -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include - -/* - This method is the one called automatically by the StelModuleMgr just - after loading the dynamic library -*/ -StelModule* MissingStarsStelPluginInterface::getStelModule() const -{ - return new MissingStars(); -} - -StelPluginInfo MissingStarsStelPluginInterface::getPluginInfo() const -{ - Q_INIT_RESOURCE(MissingStars); - - StelPluginInfo info; - info.id = "MissingStars"; - info.displayedName = N_("Missing Stars"); - info.authors = "Alexander Wolf"; - info.contact = STELLARIUM_DEV_URL; - info.description = N_("This plugin allows you to see some missing stars."); - info.version = MISSINGSTARS_PLUGIN_VERSION; - info.license = MISSINGSTARS_PLUGIN_LICENSE; - return info; -} - -/* - Constructor -*/ -MissingStars::MissingStars() -{ - setObjectName("MissingStars"); - configDialog = new MissingStarsDialog(); - //conf = StelApp::getInstance().getSettings(); - setFontSize(StelApp::getInstance().getScreenFontSize()); - connect(&StelApp::getInstance(), SIGNAL(screenFontSizeChanged(int)), this, SLOT(setFontSize(int))); -} - -/* - Destructor -*/ -MissingStars::~MissingStars() -{ - delete configDialog; -} - -void MissingStars::deinit() -{ - texPointer.clear(); -} - -/* - Reimplementation of the getCallOrder method -*/ -double MissingStars::getCallOrder(StelModuleActionName actionName) const -{ - if (actionName==StelModule::ActionDraw) - return StelApp::getInstance().getModuleMgr().getModule("StarMgr")->getCallOrder(actionName); - return 0; -} - - -/* - Init our module -*/ -void MissingStars::init() -{ - texPointer = StelApp::getInstance().getTextureManager().createTexture(StelFileMgr::getInstallationDir()+"/textures/pointeur2.png"); - - readJsonFile(); - - StarMgr* smgr = GETSTELMODULE(StarMgr); - connect(smgr, SIGNAL(starsDisplayedChanged(bool)), this, SLOT(setFlagShowStars(bool))); - connect(smgr, SIGNAL(starLabelsDisplayedChanged(bool)), this, SLOT(setFlagShowLabels(bool))); - - setFlagShowStars(true); - - GETSTELMODULE(StelObjectMgr)->registerStelObjectMgr(this); - - // key bindings and other actions - addAction("actionShow_MissingStars_ConfigDialog", N_("Missing Stars"), N_("Missing Stars configuration window"), configDialog, "visible", ""); // Allow assign shortkey -} - -/* - Draw our module. This should print name of first missing star in the main window -*/ -void MissingStars::draw(StelCore* core) -{ - if (!flagShowStars) - return; - - StelProjectorP prj = core->getProjection(StelCore::FrameJ2000); - StelPainter painter(prj); - painter.setFont(font); - - for (const auto& ms : std::as_const(missingstars)) - { - if (ms && ms->initialized) - ms->draw(core, &painter); - } - - if (GETSTELMODULE(StelObjectMgr)->getFlagSelectedObjectPointer()) - drawPointer(core, painter); -} - -void MissingStars::drawPointer(StelCore* core, StelPainter& painter) -{ - const QList newSelected = GETSTELMODULE(StelObjectMgr)->getSelectedObject("MissingStar"); - if (!newSelected.empty()) - { - const StelObjectP obj = newSelected[0]; - Vec3d pos=obj->getJ2000EquatorialPos(core); - - Vec3d screenpos; - // Compute 2D pos and return if outside screen - if (!painter.getProjector()->project(pos, screenpos)) - return; - - painter.setColor(obj->getInfoColor()); - texPointer->bind(); - painter.setBlending(true); - painter.drawSprite2dMode(static_cast(screenpos[0]), static_cast(screenpos[1]), 13.f, static_cast(StelApp::getInstance().getTotalRunTime())*40.f); - } -} - -QList MissingStars::searchAround(const Vec3d& av, double limitFov, const StelCore* core) const -{ - QList result; - - Vec3d v(av); - v.normalize(); - const double cosLimFov = cos(limitFov * M_PI/180.); - Vec3d equPos; - - for (const auto& ms : missingstars) - { - if (ms->initialized) - { - equPos = ms->getJ2000EquatorialPos(core); - equPos.normalize(); - if (equPos.dot(v) >= cosLimFov) - { - result.append(qSharedPointerCast(ms)); - } - } - } - - return result; -} - -StelObjectP MissingStars::searchByName(const QString& englishName) const -{ - for (const auto& msn : missingstars) - { - if (msn->getEnglishName().toUpper() == englishName.toUpper()) - return qSharedPointerCast(msn); - } - - return nullptr; -} - -StelObjectP MissingStars::searchByNameI18n(const QString& nameI18n) const -{ - for (const auto& msn : missingstars) - { - if (msn->getNameI18n().toUpper() == nameI18n.toUpper()) - return qSharedPointerCast(msn); - } - - return nullptr; -} - -QStringList MissingStars::listAllObjects(bool inEnglish) const -{ - QStringList result; - if (inEnglish) - { - for (const auto& msn : missingstars) - { - result << msn->getEnglishName(); - } - } - else - { - for (const auto& msn : missingstars) - { - result << msn->getNameI18n(); - } - } - return result; -} - -/* - Read the JSON file and create list of missing stars. -*/ -void MissingStars::readJsonFile(void) -{ - setMissingStarsMap(loadMissingStarsMap()); -} - -/* - Parse JSON file and load missing stars to map -*/ -QVariantMap MissingStars::loadMissingStarsMap() -{ - QVariantMap map; - QFile jsonFile(":/MissingStars/missingstars.json"); - if (jsonFile.open(QIODevice::ReadOnly)) - { - map = StelJsonParser::parse(jsonFile.readAll()).toMap(); - jsonFile.close(); - } - return map; -} - -/* - Set items for list of struct from data map -*/ -void MissingStars::setMissingStarsMap(const QVariantMap& map) -{ - missingstars.clear(); - designations.clear(); - int mscount = 0; - QVariantMap msMap = map.value("catalog").toMap(); - for (auto &msEntry : msMap) - { - QVariantMap msData = msEntry.toMap(); - msData["designation"] = msMap.key(msEntry); - - MissingStarP ms(new MissingStar(msData)); - if (ms->initialized) - { - missingstars.append(ms); - designations.append(ms->getID()); - mscount++; - } - } - qInfo().noquote() << "[MissingStars] Loaded" << mscount << "extra stars (missing in main catalogs)"; -} - -MissingStarP MissingStars::getByID(const QString& id) const -{ - for (const auto& msn : missingstars) - { - if (msn->initialized && msn->designation == id) - return msn; - } - return MissingStarP(); -} - -bool MissingStars::configureGui(bool show) -{ - if (show) - configDialog->setVisible(true); - return true; -} - -QString MissingStars::getMissingStarsList() const -{ - return designations.join(", "); -} - diff --git a/plugins/MissingStars/src/MissingStars.hpp b/plugins/MissingStars/src/MissingStars.hpp deleted file mode 100644 index 0208d3986f564..0000000000000 --- a/plugins/MissingStars/src/MissingStars.hpp +++ /dev/null @@ -1,164 +0,0 @@ -/* - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. - */ - -#ifndef MISSINGSTARS_HPP -#define MISSINGSTARS_HPP - -#include "StelObjectModule.hpp" -#include "StelObject.hpp" -#include "StelTextureTypes.hpp" -#include "MissingStar.hpp" -#include -#include -#include -#include -#include - -class QSettings; -class MissingStarsDialog; - -class StelPainter; - -/*! @defgroup missingStars Missing Stars Plug-in -@{ -The %Missing Stars plugin displays the positions some missing stars. - -Missing Stars Catalog - -The missing stars catalog is stored on the disk in [JSON](http://www.json.org/) -format, in a file named "missingstars.json". A default copy is embedded in the -plug-in at compile time. A working copy is kept in the user data directory. - -Configuration - -The plug-ins' configuration data is stored in Stellarium's main configuration -file. - -@} -*/ - -//! @ingroup missingStars -typedef QSharedPointer MissingStarP; - -//! @class MissingStars -//! Main class of the %Missing Stars plugin. -//! @author Alexander Wolf -//! @ingroup missingStars -class MissingStars : public StelObjectModule -{ - Q_OBJECT -public: - MissingStars(); - ~MissingStars() override; - - /////////////////////////////////////////////////////////////////////////// - // Methods defined in the StelModule class - void init() override; - void deinit() override; - void draw(StelCore* core) override; - virtual void drawPointer(StelCore* core, StelPainter& painter); - double getCallOrder(StelModuleActionName actionName) const override; - - /////////////////////////////////////////////////////////////////////////// - // Methods defined in StelObjectModule class - //! Used to get a list of objects which are near to some position. - //! @param v a vector representing the position in th sky around which to search for missing stars. - //! @param limitFov the field of view around the position v in which to search for missing stars. - //! @param core the StelCore to use for computations. - //! @return a list containing the missing stars located inside the limitFov circle around position v. - QList searchAround(const Vec3d& v, double limitFov, const StelCore* core) const override; - - //! Return the matching missing stars object's pointer if exists or nullptr. - //! @param nameI18n The case in-sensitive localized star name - StelObjectP searchByNameI18n(const QString& nameI18n) const override; - - //! Return the matching missing star if exists or nullptr. - //! @param name The case in-sensitive english star name - StelObjectP searchByName(const QString& name) const override; - - //! Return the matching missing star if exists, or an "empty" pointer. - //! @param id The missing star id - StelObjectP searchByID(const QString &id) const override - { - return qSharedPointerCast(getByID(id)); - } - - QStringList listAllObjects(bool inEnglish) const override; - - QString getName() const override { return "Missing Stars"; } - QString getStelObjectType() const override { return MissingStar::MISSINGSTAR_TYPE; } - - //! get a star object by identifier - MissingStarP getByID(const QString& id) const; - - //! Get list of designations for missing stars - QString getMissingStarsList() const; - - //! Implement this to tell the main Stellarium GUI that there is a GUI element to configure this - //! plugin. - bool configureGui(bool show=true) override; - -public slots: - //! Connect this to StelApp font size. - void setFontSize(int s){font.setPixelSize(s);} - -private slots: - void setFlagShowStars(const bool b) { flagShowStars = b; } - void setFlagShowLabels(const bool b) { MissingStar::flagShowLabels = b; } - -private: - // Font used for displaying our text - QFont font; - - //! Read the JSON file and create list of missing stars. - void readJsonFile(void); - - //! Parse JSON file and load missing stars to map - QVariantMap loadMissingStarsMap(); - - //! Set items for list of struct from data map - void setMissingStarsMap(const QVariantMap& map); - - StelTextureSP texPointer; - QList missingstars; - QStringList designations; - - //QSettings* conf; - - bool flagShowStars; - - // GUI - MissingStarsDialog* configDialog; -}; - -#include -#include "StelPluginInterface.hpp" - -//! This class is used by Qt to manage a plug-in interface -class MissingStarsStelPluginInterface : public QObject, public StelPluginInterface -{ - Q_OBJECT - Q_PLUGIN_METADATA(IID StelPluginInterface_iid) - Q_INTERFACES(StelPluginInterface) -public: - StelModule* getStelModule() const override; - StelPluginInfo getPluginInfo() const override; - //QObjectList getExtensionList() const override { return QObjectList(); } -}; - -#endif /* MISSINGSTARS_HPP */ diff --git a/plugins/MissingStars/src/gui/MissingStarsDialog.cpp b/plugins/MissingStars/src/gui/MissingStarsDialog.cpp deleted file mode 100644 index 523e8bdf65688..0000000000000 --- a/plugins/MissingStars/src/gui/MissingStarsDialog.cpp +++ /dev/null @@ -1,105 +0,0 @@ -/* - * Stellarium Missing Stars Plug-in GUI - * - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. -*/ - -#include -#include - -#include "StelApp.hpp" -#include "ui_missingStarsDialog.h" -#include "MissingStarsDialog.hpp" -#include "MissingStars.hpp" -#include "StelModuleMgr.hpp" -#include "StelStyle.hpp" -#include "StelGui.hpp" -#include "StelTranslator.hpp" - -MissingStarsDialog::MissingStarsDialog() - : StelDialog("MissingStars") - , msm(nullptr) -{ - ui = new Ui_missingStarsDialog; -} - -MissingStarsDialog::~MissingStarsDialog() -{ - delete ui; -} - -void MissingStarsDialog::retranslate() -{ - if (dialog) - { - ui->retranslateUi(dialog); - setAboutHtml(); - } -} - -// Initialize the dialog widgets and connect the signals/slots -void MissingStarsDialog::createDialogContent() -{ - msm = GETSTELMODULE(MissingStars); - ui->setupUi(dialog); - ui->tabs->setCurrentIndex(0); - connect(&StelApp::getInstance(), SIGNAL(languageChanged()), - this, SLOT(retranslate())); - - // Kinetic scrolling - kineticScrollingList << ui->aboutTextBrowser; - StelGui* gui= dynamic_cast(StelApp::getInstance().getGui()); - if (gui) - { - enableKineticScrolling(gui->getFlagUseKineticScrolling()); - connect(gui, SIGNAL(flagUseKineticScrollingChanged(bool)), this, SLOT(enableKineticScrolling(bool))); - } - - connect(ui->titleBar, &TitleBar::closeClicked, this, &StelDialog::close); - connect(ui->titleBar, SIGNAL(movedTo(QPoint)), this, SLOT(handleMovedTo(QPoint))); - - // About tab - setAboutHtml(); - if(gui!=nullptr) - ui->aboutTextBrowser->document()->setDefaultStyleSheet(QString(gui->getStelStyle().htmlStyleSheet)); -} - -void MissingStarsDialog::setAboutHtml(void) -{ - QString html = ""; - html += "

" + q_("Missing Stars Plug-in") + "

"; - html += ""; - html += ""; - html += ""; - html += "
" + q_("Version") + ":" + MISSINGSTARS_PLUGIN_VERSION + "
" + q_("License") + ":" + MISSINGSTARS_PLUGIN_LICENSE + "
" + q_("Author") + ":Alexander Wolf
"; - - html += "

" + q_("This plugin allows you to see some missing stars: "); - html += msm->getMissingStarsList(); - html += "

"; - - html += StelApp::getInstance().getModuleMgr().getStandardSupportLinksInfo("Missing Stars plugin"); - html += ""; - - StelGui* gui = dynamic_cast(StelApp::getInstance().getGui()); - if(gui!=nullptr) - { - QString htmlStyleSheet(gui->getStelStyle().htmlStyleSheet); - ui->aboutTextBrowser->document()->setDefaultStyleSheet(htmlStyleSheet); - } - - ui->aboutTextBrowser->setHtml(html); -} diff --git a/plugins/MissingStars/src/gui/MissingStarsDialog.hpp b/plugins/MissingStars/src/gui/MissingStarsDialog.hpp deleted file mode 100644 index 9c7efc9b90bf0..0000000000000 --- a/plugins/MissingStars/src/gui/MissingStarsDialog.hpp +++ /dev/null @@ -1,54 +0,0 @@ -/* - * Stellarium Missing Stars Plug-in GUI - * - * Copyright (C) 2023 Alexander Wolf - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License - * as published by the Free Software Foundation; either version 2 - * of the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA. -*/ - -#ifndef MISSINGSTARSDIALOG_HPP -#define MISSINGSTARSDIALOG_HPP - -#include -#include "StelDialog.hpp" -#include "MissingStars.hpp" - -class Ui_missingStarsDialog; -class QTimer; -class MissingStars; - -//! @ingroup missingStars -class MissingStarsDialog : public StelDialog -{ - Q_OBJECT - -public: - MissingStarsDialog(); - ~MissingStarsDialog() override; - -protected: - //! Initialize the dialog widgets and connect the signals/slots - void createDialogContent() override; - -public slots: - void retranslate() override; - -private: - MissingStars* msm; - Ui_missingStarsDialog* ui; - void setAboutHtml(void); -}; - -#endif // MISSINGSTARSDIALOG_HPP diff --git a/plugins/MissingStars/src/gui/missingStarsDialog.ui b/plugins/MissingStars/src/gui/missingStarsDialog.ui deleted file mode 100644 index aa528243a81e9..0000000000000 --- a/plugins/MissingStars/src/gui/missingStarsDialog.ui +++ /dev/null @@ -1,83 +0,0 @@ - - - missingStarsDialog - - - - 0 - 0 - 530 - 334 - - - - Missing Stars Configuration - - - - 0 - - - 0 - - - 0 - - - 0 - - - 0 - - - - - Missing Stars Plug-in Configuration - - - - - - - false - - - - About - - - - 9 - - - - - true - - - true - - - - - - - - - - - - TitleBar - QFrame -
Dialog.hpp
- 1 - - - StelCloseButton - QPushButton -
gui/StelCloseButton.hpp
- - - - - diff --git a/src/core/StelApp.cpp b/src/core/StelApp.cpp index f7a415d984092..db01723ce5e7e 100644 --- a/src/core/StelApp.cpp +++ b/src/core/StelApp.cpp @@ -160,10 +160,6 @@ Q_IMPORT_PLUGIN(LensDistortionEstimatorStelPluginInterface) Q_IMPORT_PLUGIN(MeteorShowersStelPluginInterface) #endif -#ifdef USE_STATIC_PLUGIN_MISSINGSTARS -Q_IMPORT_PLUGIN(MissingStarsStelPluginInterface) -#endif - #ifdef USE_STATIC_PLUGIN_NAVSTARS Q_IMPORT_PLUGIN(NavStarsStelPluginInterface) #endif diff --git a/src/gui/SearchDialog.cpp b/src/gui/SearchDialog.cpp index b4af189e3ee39..b18c2e5809e3f 100644 --- a/src/gui/SearchDialog.cpp +++ b/src/gui/SearchDialog.cpp @@ -1367,7 +1367,6 @@ void SearchDialog::gotoObjectWithType(const QModelIndex &modelIndex) objType.replace("Pulsars","Pulsar"); objType.replace("Quasars","Quasar"); objType.replace("MeteorShowers","MeteorShower"); - objType.replace("MissingStars","MissingStar"); gotoObject(modelIndex.model()->data(modelIndex, Qt::DisplayRole).toString(), objType); }