Also update CHANGES file.
The compiler warnings were issued by MinGW with gcc 9.2.0.
Note: There are lots of compiler warnings left when building with
Visual Studio and/or NMake but these will not be fixed in 1.3.9.
All warnings have been fixed in 1.4.0 (current git 'master').
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).
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
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".
Select the "best" target rather than a random one out of a list of
suitable targets. The target selection algorithm would sometimes
select the wrong target and hence retrieve unexpected data.
This could happen in both copy-paste and drag-and-drop operations.
- fix undefined 'GC' if no window has been shown/drawn yet
- may still need to call fl_open_display() prior to offscreen-drawing
- improve documentation, add example code
Fix bug in CMake/posixScandir.cxx (backported from 1.4).
Fix table structure in test/help-test.html (backported from 1.4).
Clarify that the deprecated forms compatibility *may* be removed in
FLTK 1.4
Revert commit 958d912ffc using 'XSetLocaleModifiers("@im=");'
which was incorrect (STR 3192).
Apply fix for STR 3502, using 'XSetLocaleModifiers("");' which appears
to be the correct solution for using X Input Methods (XIM).
The given position to insert a new item was not checked against the
valid range so the program could crash if a position less than zero
or greater than children() was given. The position is now clamped to
the valid range, i.e. the item is either prepended or appended.
Fixes issue #18.
Backported from 1.4, commit 9b272cfa4e
CHANGES: update list of changes.
KNOWN_BUGS.html: prepare list of open bugs (currently empty).
Todo: add actual bug list to KNOWN_BUGS.html before release.
This patch fixes two aspects described in STR #3119:
(a) enables detection and prefers pixel formats with composition
(b) selects no more than 32 bit colors (8 bits per pixel)
(a) was the reason for this STR, (b) was reported repeatedly in
fltk.general (see STR #3119).
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@13112 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Some border lines were too short or too long, the shading code would draw
too many shaded lines, and the code was hard to understand.
With this commit all background pixels of the box are drawn exactly once.
The border lines are consistent, but some pixels of the border are not
drawn at all so the background shines through. This is intended for
backwards compatibility.
A minor change is that the drawn background does no longer overlap the
border lines. Hence undrawn pixels that previously displayed the colored
box background are now transparent and show the parent widget's color.
This commit adds comments and implementation notes to make the code easier
to understand and better maintainable (hopefully).
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@12778 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
See fltk.general "Fl_Text_Buffer constructor bug" on Dec 5, 2016.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@12335 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
