This support becomes very difficult with recent macOS versions for the
approach used in 1.3 based on undefining __APPLE__.
[In contrast, the approach used in 1.4 that doesn't mess with __APPLE__
is still compatible with recent macOS versions].
This commit removes an unused variable as suggested in the discussion
of issue #445: "type issue in fluid/ExternalCodeEditor_WIN32.cxx"
Backported from 'master', b5b88d5f0d
Note: this "type issue" made the build fail on Windows with current
MSYS2 (gcc 13.1.0).
- update header comment and copyright year
- add casts to fix compiler warnings
- fix "use after free" warning
- remove dead code
- reformat another unrelated statement
FLTK 1.3.x code relies on WIN32 being defined (rather than _WIN32).
This commit defines WIN32 on Windows builds unless Cygwin (__CYGWIN__)
is used to avoid the common user error to "forget" to define WIN32 on
the commandline or in the build system (e.g. Visual Studio).
This old code (unchanged since 1998) wouldn't compile with the current
version of Visual Studio 2022.
Fix backported from 1.4.0 (c4bb4e192e).
Original commit by Matthias Melcher.
Suppress warning [-Wdeprecated-declarations] regarding function
XKeycodeToKeysym()
Backported from master branch.
Update 'CHANGES' for a potential release 1.3.9
Reading large selections via X11 INCR protocol (data sent by other
processes) could cause invalid write access and eventually segfaults.
For more information see GitHub issue #451 and these commits in
FLTK 1.4 (master branch):
- c555629162
- ef72df0dc7
This commit fixes the main issues when reading large selections via
INCR protocol but does not add functionality to *write* large
selections via INCR protocol.
This new dialog enables the user program to distinguish whether the
user closed the window by hitting Escape, clicking the window's
close button, or using the "cancel" button with return value 0
as requested by GitHub Issue #282 "fl_choice() doesn't tell you
if the dialog was closed".
This undocumented macro is used on X11 and macOS platforms to
consolidate mouse move events, i.e. to collect some events and send
them later as one event. The old macro name CONSOLIDATE_MOTION has been
renamed to FLTK_CONSOLIDATE_MOTION since it is now a "global" symbol.
Users can define FLTK_CONSOLIDATE_MOTION in their build system, e.g.
on the compiler commandline, as 0 or 1 to disable or enable this
feature, respectively.
For historical reasons the default is 0 (OFF) on macOS and 1 (ON) on
X11 in FLTK 1.3. In FLTK 1.4 the default will always be 0 (OFF).
