From f09e17c3c564e8310125a10c03397cbf473ff643 Mon Sep 17 00:00:00 2001 From: Albrecht Schlosser Date: Wed, 1 Jul 2020 18:03:10 +0200 Subject: Remove $Id$ tags, update URL's, and more - remove obsolete svn '$Id$' tags from all source files - update .fl files and generated files accordingly - replace 'http://www.fltk.org' URL's with 'https://...' - replace bug report URL 'str.php' with 'bugs.php' - remove trailing whitespace - fix other whitespace errors flagged by Git - add and/or fix missing or wrong standard headers - convert tabs to spaces in all source files The only relevant code changes are in the fluid/ folder where some .fl files and other source files were used to generate the '$Id' headers and footers. --- documentation/src/osissues.dox | 178 ++++++++++++++++++++--------------------- 1 file changed, 89 insertions(+), 89 deletions(-) (limited to 'documentation/src/osissues.dox') diff --git a/documentation/src/osissues.dox b/documentation/src/osissues.dox index e2511f4ef..d629acfab 100644 --- a/documentation/src/osissues.dox +++ b/documentation/src/osissues.dox @@ -1,6 +1,6 @@ /** - \page osissues Operating System Issues + \page osissues Operating System Issues This appendix describes the operating system specific interfaces in FLTK: \li \ref osissues_accessing @@ -21,24 +21,24 @@ This header file will define the appropriate interface for your environment. The pages that follow describe the functionality that is provided for each operating system. -\note These definitions used to be in FL/x.H up to FLTK 1.3.x. Usage of - FL/x.H is deprecated since FLTK 1.4.0. You should replace all references - of FL/x.H with FL/platform.H if your target is FLTK 1.4 or later. - FL/x.H will be retained for backwards compatibility for some - releases but will be removed in a later (not yet specified) - FLTK release. +\note These definitions used to be in FL/x.H up to FLTK 1.3.x. Usage of + FL/x.H is deprecated since FLTK 1.4.0. You should replace all references + of FL/x.H with FL/platform.H if your target is FLTK 1.4 or later. + FL/x.H will be retained for backwards compatibility for some + releases but will be removed in a later (not yet specified) + FLTK release.
- +
WARNING: + WARNING: - The interfaces provided by this header file may - change radically in new FLTK releases. Use them only - when an existing generic FLTK interface is not - sufficient. + The interfaces provided by this header file may + change radically in new FLTK releases. Use them only + when an existing generic FLTK interface is not + sufficient. -
@@ -157,7 +157,7 @@ int fl_parse_color(const char* p, uchar& r, uchar& g, uchar& b) Convert a name into the red, green, and blue values of a color by parsing the X11 color names. On other systems, \c fl_parse_color() can only convert names in hexadecimal encoding, for example \#ff8083. - + extern XFontStruct *fl_xfont \par @@ -167,7 +167,7 @@ This is not necessarily the current font of \c fl_gc, which is not set until \ref ssect_Text "fl_draw()" is called. If FLTK was compiled with Xft support, \c fl_xfont -will usually be 0 and \c fl_xftfont will contain a pointer +will usually be 0 and \c fl_xftfont will contain a pointer to the \c XftFont structure instead. extern void *fl_xftfont @@ -176,7 +176,7 @@ extern void *fl_xftfont If FLTK was compiled with Xft support enabled, \c fl_xftfont points to the xft font selected by the most recent \ref ssect_Fonts "fl_font()". -Otherwise it will be 0. \c fl_xftfont should be cast to +Otherwise it will be 0. \c fl_xftfont should be cast to XftFont*. \subsection osissues_xvisual Changing the Display, Screen, or X Visual @@ -283,7 +283,7 @@ An example: \code void MyWindow::show() { if (shown()) {Fl_Window::show(); return;} // you must do this! - fl_open_display(); // necessary if this is first window + fl_open_display(); // necessary if this is first window // we only calculate the necessary visual colormap once: static XVisualInfo *visual; static Colormap colormap; @@ -428,13 +428,13 @@ of libraries that are used to link the application (usually "-lXpm").
- +
NOTE: - - You must call Fl_Window::show(int argc, char** argv) - for the icon to be used. The Fl_Window::show() method - does not bind the icon to the window. + NOTE: + + You must call Fl_Window::show(int argc, char** argv) + for the icon to be used. The Fl_Window::show() method + does not bind the icon to the window. -
@@ -446,27 +446,27 @@ Fl_Window::show(int argc, char** argv) method is called, FLTK looks for the following X resources: \li \c background - The default background color - for widgets (color). + for widgets (color). \li \c dndTextOps - The default setting for - drag and drop text operations (boolean). + drag and drop text operations (boolean). \li \c foreground - The default foreground (label) - color for widgets (color). + color for widgets (color). \li \c scheme - The default scheme to use (string). \li \c selectBackground - The default selection - color for menus, etc. (color). + color for menus, etc. (color). \li Text.background - The default background - color for text fields (color). + color for text fields (color). \li \c tooltips - The default setting for - tooltips (boolean). + tooltips (boolean). \li \c visibleFocus - The default setting for - visible keyboard focus on non-text widgets (boolean). + visible keyboard focus on non-text widgets (boolean). Resources associated with the first window's Fl_Window::xclass() string are queried first, or if no class has been specified then @@ -488,7 +488,7 @@ state information and data structures. \subsection non_ascii_filenames Using filenames with non-ASCII characters In FLTK, all strings, including filenames, are UTF-8 encoded. The utility functions -fl_fopen() and fl_open() allow to open files potentially having non-ASCII names in a +fl_fopen() and fl_open() allow to open files potentially having non-ASCII names in a cross-platform fashion, whereas the standard fopen()/open() functions fail to do so. \subsection osissues_wm_quit Responding to WM_QUIT @@ -615,13 +615,13 @@ bitmap data.
- +
NOTE: - - You must call Fl_Window::show(int argc, char** argv) - for the icon to be used. The Fl_Window::show() method - does not bind the icon to the window. + NOTE: + + You must call Fl_Window::show(int argc, char** argv) + for the icon to be used. The Fl_Window::show() method + does not bind the icon to the window. -
@@ -656,32 +656,32 @@ them in the foreground. The following is a list of known bugs and problems in the Windows version of FLTK: -\li If a program is deactivated, Fl::wait() - does not return until it is activated again, even though - many events are delivered to the program. This can cause - idle background processes to stop unexpectedly. This - also happens while the user is dragging or resizing - windows or otherwise holding the mouse down. We were - forced to remove most of the efficiency FLTK uses for - redrawing in order to get windows to update while being - moved. This is a design error in Windows and probably - impossible to get around. - -\li Fl_Gl_Window::can_do_overlay() returns true - until the first time it attempts to draw an overlay, and - then correctly returns whether or not there is overlay - hardware. - -\li SetCapture (used by Fl::grab()) - doesn't work, and the main window title bar turns gray - while menus are popped up. - -\li Compilation with gcc 3.4.4 and -Os exposes an - optimisation bug in gcc. The symptom is that when drawing - filled circles only the perimeter is drawn. This can for instance - be seen in the symbols demo. Other optimisation options such - as -O2 and -O3 seem to work OK. More details can be found - in STR#1656 +\li If a program is deactivated, Fl::wait() + does not return until it is activated again, even though + many events are delivered to the program. This can cause + idle background processes to stop unexpectedly. This + also happens while the user is dragging or resizing + windows or otherwise holding the mouse down. We were + forced to remove most of the efficiency FLTK uses for + redrawing in order to get windows to update while being + moved. This is a design error in Windows and probably + impossible to get around. + +\li Fl_Gl_Window::can_do_overlay() returns true + until the first time it attempts to draw an overlay, and + then correctly returns whether or not there is overlay + hardware. + +\li SetCapture (used by Fl::grab()) + doesn't work, and the main window title bar turns gray + while menus are popped up. + +\li Compilation with gcc 3.4.4 and -Os exposes an + optimisation bug in gcc. The symptom is that when drawing + filled circles only the perimeter is drawn. This can for instance + be seen in the symbols demo. Other optimisation options such + as -O2 and -O3 seem to work OK. More details can be found + in STR#1656 \section osissues_macos The Apple OS X Interface @@ -707,8 +707,8 @@ Right Click simulation with Ctrl Click The Apple HIG guidelines indicate applications should support 'Ctrl Click' to simulate 'Right Click' for e.g. context menus, so users with one-button mice and one-click trackpads can still -access right-click features. However, paraphrasing - +access right-click features. However, paraphrasing + Manolo's comment on the fltk.coredev newsgroup: \par