Skip to content

Commit 8cb3be3

Browse files
committed
Initial import of the sourcecode.
1 parent 533eac7 commit 8cb3be3

File tree

192 files changed

+50738
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

192 files changed

+50738
-0
lines changed

doc/Unused parts of API.txt

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
The following parts of the SysTabControl32 API (Windows 10) are not used:
2+
3+
Control styles:
4+
---------------
5+
- TCS_FOCUSNEVER (https://msdn.microsoft.com/en-us/library/ms650931.aspx)
6+
-> would require different OLEMISC_* flags and therefore can't be implemented without creating an additional control
7+
8+
Messages:
9+
---------
10+
- TCM_REMOVEIMAGE (https://msdn.microsoft.com/en-us/library/ms651064.aspx)
11+
-> questionable benefits
12+
-> can be used easily via SendMessage()
13+
- TCM_SETITEMEXTRA (https://msdn.microsoft.com/en-us/library/ms651070.aspx)
14+
-> too difficult to handle, because we would need a way to make the ITabStripTab::TabData property accept data of the correct size only
15+
-> probably noone really needs this feature
16+
17+
Notifications:
18+
--------------
19+
- TCN_KEYDOWN (https://msdn.microsoft.com/en-us/library/ms650956.aspx)
20+
-> doesn't seem to have any benefit over WM_KEYDOWN
21+
22+
Flags:
23+
------
24+
- TCITEM/TCIF_RTLREADING (https://msdn.microsoft.com/en-us/library/ms650940.aspx)
25+
-> can't be used because there's no way to retrieve whether a tab has this flag set
26+
27+
Other:
28+
------
29+
- Support for multiple (drop-)highlighted tabs
30+
-> SysTabControl32 can have more than one highlighted tab at once
Lines changed: 284 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,284 @@
1+
# Doxyfile 1.7.3
2+
3+
# This file describes the settings to be used by the documentation system
4+
# doxygen (www.doxygen.org) for a project
5+
#
6+
# All text after a hash (#) is considered a comment and will be ignored
7+
# The format is:
8+
# TAG = value [value, ...]
9+
# For lists items can also be appended using:
10+
# TAG += value [value, ...]
11+
# Values that contain spaces should be placed between quotes (" ")
12+
13+
#---------------------------------------------------------------------------
14+
# Project related configuration options
15+
#---------------------------------------------------------------------------
16+
17+
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
18+
# by quotes) that should identify the project.
19+
20+
PROJECT_NAME = "TimoSoft TabStrip"
21+
22+
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
23+
# This could be handy for archiving the generated documentation or
24+
# if some version control system is used.
25+
26+
PROJECT_NUMBER = 1.10.3.175
27+
28+
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
29+
# base path where the generated documentation will be put.
30+
# If a relative path is entered, it will be relative to the location
31+
# where doxygen was started. If left blank the current directory will be used.
32+
33+
OUTPUT_DIRECTORY = help/ANSI/Doxygen/private
34+
35+
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
36+
# path before files name in the file list and in the header files. If set
37+
# to NO the shortest path that makes the file name unique will be used.
38+
39+
FULL_PATH_NAMES = NO
40+
41+
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
42+
# Doxygen uses this value to replace tabs by spaces in code fragments.
43+
44+
TAB_SIZE = 2
45+
46+
# This tag can be used to specify a number of aliases that acts
47+
# as commands in the documentation. An alias has the form "name=value".
48+
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
49+
# put the command \sideeffect (or @sideeffect) in the documentation, which
50+
# will result in a user-defined paragraph with heading "Side Effects:".
51+
# You can put \n's in the value part of an alias to insert newlines.
52+
53+
ALIASES = "usedin=\par Used in following samples:\n"
54+
55+
# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
56+
# according to the Markdown format, which allows for more readable
57+
# documentation. See http://daringfireball.net/projects/markdown/ for details.
58+
# The output of markdown processing is further processed by doxygen, so you can
59+
# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
60+
# case of backward compatibilities issues.
61+
# The default value is: YES.
62+
63+
MARKDOWN_SUPPORT = NO
64+
65+
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
66+
# to include (a tag file for) the STL sources as input, then you should
67+
# set this tag to YES in order to let doxygen match functions declarations and
68+
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
69+
# func(std::string) {}). This also makes the inheritance and collaboration
70+
# diagrams that involve STL classes more complete and accurate.
71+
72+
BUILTIN_STL_SUPPORT = YES
73+
74+
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
75+
# tag is set to YES, then doxygen will reuse the documentation of the first
76+
# member in the group (if any) for the other members of the group. By default
77+
# all members of a group must be documented explicitly.
78+
79+
DISTRIBUTE_GROUP_DOC = YES
80+
81+
#---------------------------------------------------------------------------
82+
# Build related configuration options
83+
#---------------------------------------------------------------------------
84+
85+
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
86+
# will be included in the documentation.
87+
88+
EXTRACT_PRIVATE = YES
89+
90+
# If the EXTRACT_STATIC tag is set to YES all static members of a file
91+
# will be included in the documentation.
92+
93+
EXTRACT_STATIC = YES
94+
95+
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
96+
# undocumented members of documented classes, files or namespaces.
97+
# If set to NO (the default) these members will be included in the
98+
# various overviews, but no documentation section is generated.
99+
# This option has no effect if EXTRACT_ALL is enabled.
100+
101+
HIDE_UNDOC_MEMBERS = YES
102+
103+
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
104+
# undocumented classes that are normally visible in the class hierarchy.
105+
# If set to NO (the default) these classes will be included in the various
106+
# overviews. This option has no effect if EXTRACT_ALL is enabled.
107+
108+
HIDE_UNDOC_CLASSES = YES
109+
110+
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
111+
# documentation blocks found inside the body of a function.
112+
# If set to NO (the default) these blocks will be appended to the
113+
# function's detailed documentation block.
114+
115+
HIDE_IN_BODY_DOCS = YES
116+
117+
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
118+
# will show members with their full class and namespace scopes in the
119+
# documentation. If set to YES the scope will be hidden.
120+
121+
HIDE_SCOPE_NAMES = YES
122+
123+
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
124+
# will put a list of the files that are included by a file in the documentation
125+
# of that file.
126+
127+
SHOW_INCLUDE_FILES = NO
128+
129+
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
130+
# will sort the (detailed) documentation of file and class members
131+
# alphabetically by member name. If set to NO the members will appear in
132+
# declaration order.
133+
134+
SORT_MEMBER_DOCS = NO
135+
136+
# The ENABLED_SECTIONS tag can be used to enable conditional
137+
# documentation sections, marked by \if sectionname ... \endif.
138+
139+
ENABLED_SECTIONS = PRIVATEDOC \
140+
ANSI
141+
142+
#---------------------------------------------------------------------------
143+
# configuration options related to the input files
144+
#---------------------------------------------------------------------------
145+
146+
# The INPUT tag can be used to specify the files and/or directories that contain
147+
# documented source files. You may enter file names like "myfile.cpp" or
148+
# directories like "/usr/src/myproject". Separate the files or directories
149+
# with spaces.
150+
151+
INPUT = src
152+
153+
# If the value of the INPUT tag contains directories, you can use the
154+
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
155+
# and *.h) to filter out the source-files in the directories. If left
156+
# blank the following patterns are tested:
157+
# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
158+
# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
159+
# *.f90 *.f *.for *.vhd *.vhdl
160+
161+
FILE_PATTERNS = *.c \
162+
*.cpp \
163+
*.c++ \
164+
*.h \
165+
*.idl
166+
167+
# If the value of the INPUT tag contains directories, you can use the
168+
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
169+
# certain files from those directories. Note that the wildcards are matched
170+
# against the file with absolute path, so to exclude all test directories
171+
# for example use the pattern */test/*
172+
173+
EXCLUDE_PATTERNS = TabStripCtlU.idl \
174+
*_in.*
175+
176+
#---------------------------------------------------------------------------
177+
# configuration options related to source browsing
178+
#---------------------------------------------------------------------------
179+
180+
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
181+
# will generate a verbatim copy of the header file for each class for
182+
# which an include is specified. Set to NO to disable this.
183+
184+
VERBATIM_HEADERS = NO
185+
186+
#---------------------------------------------------------------------------
187+
# configuration options related to the HTML output
188+
#---------------------------------------------------------------------------
189+
190+
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
191+
# documentation will contain sections that can be hidden and shown after the
192+
# page has loaded. For this to work a browser that supports
193+
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
194+
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
195+
196+
HTML_DYNAMIC_SECTIONS = YES
197+
198+
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
199+
# will be generated that can be used as input for tools like the
200+
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
201+
# of the generated HTML documentation.
202+
203+
GENERATE_HTMLHELP = YES
204+
205+
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
206+
# be used to specify the file name of the resulting .chm file. You
207+
# can add a path in front of the file if the result should not be
208+
# written to the html output directory.
209+
210+
CHM_FILE = D:\Projects\TabStripControl\help\ANSI\Doxygen\private\chm\TabStrip.chm
211+
212+
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
213+
# be used to specify the location (absolute path including file name) of
214+
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
215+
# the HTML help compiler on the generated index.hhp.
216+
217+
HHC_LOCATION = "C:\Program Files (x86)\HTML Help Workshop\hhc.exe"
218+
219+
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
220+
# structure should be generated to display hierarchical information.
221+
# If the tag value is set to YES, a side panel will be generated
222+
# containing a tree-like index structure (just like the one that
223+
# is generated for HTML Help). For this to work a browser that supports
224+
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
225+
# Windows users are probably better off using the HTML help feature.
226+
227+
GENERATE_TREEVIEW = NO
228+
229+
#---------------------------------------------------------------------------
230+
# configuration options related to the LaTeX output
231+
#---------------------------------------------------------------------------
232+
233+
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
234+
# generate Latex output.
235+
236+
GENERATE_LATEX = NO
237+
238+
#---------------------------------------------------------------------------
239+
# Configuration options related to the preprocessor
240+
#---------------------------------------------------------------------------
241+
242+
# The PREDEFINED tag can be used to specify one or more macro names that
243+
# are defined before the preprocessor is started (similar to the -D option of
244+
# gcc). The argument of the tag is a list of macros of the form: name
245+
# or name=definition (no spaces). If the definition and the = are
246+
# omitted =1 is assumed. To prevent a macro definition from being
247+
# undefined via #undef or recursively expanded use the := operator
248+
# instead of the = operator.
249+
250+
PREDEFINED = DOXYGEN_SHOULD_SKIP_THIS \
251+
ANSI
252+
253+
#---------------------------------------------------------------------------
254+
# Configuration options related to the dot tool
255+
#---------------------------------------------------------------------------
256+
257+
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
258+
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
259+
# or super classes. Setting the tag to NO turns the diagrams off. Note that
260+
# this option also works with HAVE_DOT disabled, but it is recommended to
261+
# install and use dot, since it yields more powerful graphs.
262+
263+
CLASS_DIAGRAMS = NO
264+
265+
# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
266+
# the HTML output. The underlying search engine uses javascript and DHTML and
267+
# should work on any modern browser. Note that when using HTML help
268+
# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
269+
# there is already a search function so this one should typically be disabled.
270+
# For large projects the javascript based search engine can be slow, then
271+
# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
272+
# search using the keyboard; to jump to the search box use <access key> + S
273+
# (what the <access key> is depends on the OS and browser, but it is typically
274+
# <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
275+
# key> to jump into the search results window, the results can be navigated
276+
# using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
277+
# the search. The filter options can be selected when the cursor is inside the
278+
# search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
279+
# to select a filter and <Enter> or <escape> to activate or cancel the filter
280+
# option.
281+
# The default value is: YES.
282+
# This tag requires that the tag GENERATE_HTML is set to YES.
283+
284+
SEARCHENGINE = NO

0 commit comments

Comments
 (0)