]>
git.saurik.com Git - wxWidgets.git/blob - docs/doxygen/mainpages/cat_functions.h
1 /////////////////////////////////////////////////////////////////////////////
2 // Name: cat_functions.h
3 // Purpose: Functions-by-category page of the Doxygen manual
4 // Author: wxWidgets team
6 // Licence: wxWindows license
7 /////////////////////////////////////////////////////////////////////////////
12 @page page_func_cat Functions by category
14 A classification of wxWidgets functions by category.
16 @li @ref page_func_cat_appinitterm
17 @li @ref page_func_cat_procctrl
18 @li @ref page_func_cat_thread
19 @li @ref page_func_cat_file
20 @li @ref page_func_cat_networkuseros
21 @li @ref page_func_cat_string
22 @li @ref page_func_cat_dialog
23 @li @ref page_func_cat_math
24 @li @ref page_func_cat_gdi
25 @li @ref page_func_cat_printer
26 @li @ref page_func_cat_clipboard
27 @li @ref page_func_cat_misc
28 @li @ref page_func_cat_log
29 @li @ref page_func_cat_time
30 @li @ref page_func_cat_debug
31 @li @ref page_func_cat_env
32 @li @ref page_func_cat_atomic
39 @section page_func_cat_appinitterm Application initialization and termination
41 The functions in this section are used on application startup/shutdown and also
42 to control the behaviour of the main event loop of the GUI programs.
48 @li wxHandleFatalExceptions
49 @li wxInitAllImageHandlers
57 @section page_func_cat_procctrl Process control functions
59 The functions in this section are used to launch or terminate the other processes.
70 @section page_func_cat_thread Thread functions
72 The functions and macros here mainly exist to make it writing the code which may be
73 compiled in multi thread build (wxUSE_THREADS = 1) as well as in single thread
74 configuration (wxUSE_THREADS = 0).
76 For example, a static variable must be protected against simultaneous access by multiple
77 threads in the former configuration but in the latter the extra overhead of using the
78 critical section is not needed. To solve this problem, the wxCRITICAL_SECTION macro
79 may be used to create and use the critical section only when needed.
84 wxThread, wxMutex, @ref overview_thread
91 @section page_func_cat_file File functions
96 wxPathList, wxDir, wxFile, wxFileName
98 @li wxDos2UnixFilename
100 @li wxFileModificationTime
101 @li wxFileNameFromPath
110 @li wxUnix2DosFilename
114 @li wxGetWorkingDirectory
115 @li wxGetTempFileName
119 @li wxParseCommonDialogsFilter
123 @li wxSetWorkingDirectory
126 @li wxTransferFileToStream
127 @li wxTransferStreamToFile
130 @section page_func_cat_networkuseros Network, user and OS functions
132 The functions in this section are used to retrieve information about the current
133 computer and/or user characteristics.
135 @li wxGetEmailAddress
137 @li wxGetFullHostName
140 @li wxGetOsDescription
142 @li wxIsPlatformLittleEndian
143 @li wxIsPlatform64Bit
149 @section page_func_cat_string String functions
163 @section page_func_cat_dialog Dialog functions
165 Below are a number of convenience functions for getting input from the user
166 or displaying messages. Note that in these functions the last three parameters
167 are optional. However, it is recommended to pass a parent frame parameter, or
168 (in MS Windows or Motif) the wrong window frame may be brought to the front when
169 the dialog box is popped up.
172 @li wxBeginBusyCursor
174 @li wxCreateFileTipProvider
178 @li wxGenericAboutBox
179 @li wxGetColourFromUser
180 @li wxGetFontFromUser
181 @li wxGetMultipleChoices
182 @li wxGetNumberFromUser
183 @li wxGetPasswordFromUser
184 @li wxGetTextFromUser
185 @li wxGetSingleChoice
186 @li wxGetSingleChoiceIndex
187 @li wxGetSingleChoiceData
194 @section page_func_cat_math Math functions
202 @section page_func_cat_gdi GDI functions
204 The following are relevant to the GDI (Graphics Device Interface).
209 @li wxClientDisplayRect
216 @li wxMakeMetafilePlaceable
220 @section page_func_cat_printer Printer settings
222 NB: These routines are obsolete and should no longer be used!
224 The following functions are used to control PostScript printing.
225 Under Windows, PostScript output can only be sent to a file.
229 @li wxGetPrinterCommand
232 @li wxGetPrinterOptions
233 @li wxGetPrinterOrientation
234 @li wxGetPrinterPreviewCommand
235 @li wxGetPrinterScaling
236 @li wxGetPrinterTranslation
237 @li wxSetPrinterCommand
240 @li wxSetPrinterOptions
241 @li wxSetPrinterOrientation
242 @li wxSetPrinterPreviewCommand
243 @li wxSetPrinterScaling
244 @li wxSetPrinterTranslation
247 @section page_func_cat_clipboard Clipboard functions
249 These clipboard functions are implemented for Windows only.
250 The use of these functions is deprecated and the code is no longer maintained.
251 Use the wxClipboard class instead.
253 @header{wx/clipbrd.h}
258 @li wxEnumClipboardFormats
259 @li wxGetClipboardData
260 @li wxGetClipboardFormatName
261 @li wxIsClipboardFormatAvailable
263 @li wxRegisterClipboardFormat
264 @li wxSetClipboardData
267 @section page_func_cat_misc Miscellaneous functions and macros
270 @li wxBase64DecodedSize
272 @li wxBase64EncodedSize
278 @li wxEnableTopLevelWindows
280 @li wxFindWindowByLabel
281 @li wxFindWindowByName
282 @li wxFindWindowAtPoint
283 @li wxFindWindowAtPointer
284 @li wxGetActiveWindow
285 @li wxGetBatteryState
288 @li wxGetMousePosition
291 @li wxGetTopLevelParent
292 @li wxLaunchDefaultBrowser
293 @li wxLoadUserResource
300 @section page_func_cat_log Log functions
302 These functions provide a variety of logging functions: see @ref overview_log for
303 further information. The functions use (implicitly) the currently active log target,
304 so their descriptions here may not apply if the log target is not the standard one
305 (installed by wxWidgets in the beginning of the program).
321 @li wxSafeShowMessage
328 @section page_func_cat_time Time functions
330 The functions in this section deal with getting the current time and sleeping
331 for the specified time interval.
334 @li wxGetLocalTimeMillis
343 @section page_func_cat_debug Debugging macros and functions
345 Useful macros and functions for error checking and defensive programming.
346 wxWidgets defines three families of the assert-like macros: the wxASSERT and wxFAIL
347 macros only do anything if __WXDEBUG__ is defined (in other words, in the debug build)
348 but disappear completely in the release build. On the other hand, the wxCHECK macros
349 stay event in release builds but a check failure doesn't generate any user-visible effects
350 then. Finally, the compile time assertions don't happen during the run-time but result
351 in the compilation error messages if the condition they check fail.
357 @li wxIsDebuggerRunning
360 @section page_func_cat_env Environment access functions
362 The functions in this section allow to access (get) or change value of environment
363 variables in a portable way. They are currently implemented under Win32 and
364 POSIX-like systems (Unix).
374 @section page_func_cat_atomic Atomic operation functions
376 When using multi-threaded applications, it is often required to access or modify
377 memory which is shared between threads. Atomic integer and pointer operations are
378 an efficient way to handle this issue (another, less efficient, way is to use a mutex
379 or critical section). A native implementation exists for Windows, Linux, Solaris and
380 Mac OS X, for other OS, a wxCriticalSection is used to protect the data.
382 One particular application is reference counting (used by so-called smart pointers).
384 You should define your variable with the type wxAtomicInt in order to apply atomic operations to it.