| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Make clear that outside labels of widgets are not considered when
calculating the bounding box of the children (scroll area) and
include a hint to add an invisible box if necessary.
|
|
Under the X11 platform, class Fl_Native_File_Chooser will behave as follows :
- if the KDE desktop is used and if command "kdialog" is available in the path,
the Qt/KDE file chooser is used;
- otherwise, if the GTK library is available at run-time,
the GTK file chooser is used;
- otherwise, the FLTK file chooser is used.
In addition, when Fl::OPTION_FNFC_USES_GTK is off, the FLTK file chooser
is always used.
|
|
"Tiny window problem if child group larger than window"
See Greg's comment 4: "something is wrong here: either the logic or
the docs are incorrect, not sure which."
It turned out that both were incorrect.
Since we fixed the code this commit completes the STR by fixing the
docs as well so they match the behavior.
|
|
This message icon label (usually one character) will be used in the
next call of one of the common dialogs.
test/ask.cxx: use fl_message_icon_label()
|
|
The previous name existed already with different case (fl_string.h)
in the FL folder which broke the build on macOS and Windows.
This may be a temporary fix - until I find a better way.
|
|
Apply Fl_Dialog_r10831.patch as given in STR 3242:
https://www.fltk.org/strfiles/3242/Fl_Dialog_r10831.patch
Reformat, add missing pieces, rename private members, cleanup...
Improve documentation, add fl_choice_n() (issue #282)
New methods fl_input_str() and fl_password_str() return Fl_String
|
|
This class will be used in fl_input_str() and fl_password_str().
Todo: add missing documentation ...
|
|
|
|
|
|
Also, rename fl_capture_window_part() to fl_capture_window().
|
|
|
|
No code changes.
Replace '#define fl_clip ..' with an inline method.
|
|
This new function can and should be used to draw check marks
in widgets that need it, e.g. Fl_Check_Browser (issue #68) and
Fl_Check_Button.
|
|
|
|
The new function fl_write_png() was moved to its own file and is now
publicly available ("exported") so other programs can use it.
This function was used in fluid to write a window screenshot (.png)
together with a template (.fl) to preferences storage.
|
|
Fl_Surface_Device::push_current.
|
|
|
|
no code changes
|
|
This could happen if both FL/fl_ask.H and fluid/Fl_Type.h were
included in the same file.
|
|
Declare Fl_Scroll::bbox() and Fl_Scroll::recalc_scrollbars() 'const'.
These methods don't change the Fl_Scroll widget.
Use Fl_Scroll::recalc_scrollbars() in Fl_Scroll::bbox() to simplify
the code and to avoid code duplication.
bbox() can now be called at any time and returns the correct values,
no matter if draw() has been called before.
|
|
Document clearly that reading from memory w/o the length argument
(old constructor) is discouraged (deprecated).
|
|
- use new features of Fl_Image_Reader (read error and EOF checks)
- add length argument to constructor reading from memory
|
|
- add error and EOF checks
- fix transparent pixel index outside ColorMap (#271)
- fix Fl_GIF_Image decoder bug (#274)
- add Fl_Image_Reader::skip(unsigned int)
- use new skip() method in GIF reader
|
|
Try to explain what count() returns and what data() contains which
can be different by image type.
|
|
Also:
- remove unnecessary 'size_t' conversions from FL/fl_casts.H
- add reverse conversions from integer types to 'void *'
|
|
|
|
|
|
|
|
I compiled with `-Wextra-semi -Werror=extra-semi` on Linux and Windows
(cross-compiled on Linux) and removed all "extra semicolon" warnings
I could find. I didn't check on macOS (yet).
Note: Linux configured with and w/o Pango but not w/o Xft. Compilation
with other options (e.g. Cairo) might still emit such warnings.
|
|
One less warning, yay !
|
|
|
|
|
|
|
|
This is a convenience method that does range checking (index n),
removes the child given by index n from the group and deletes it.
|
|
Apple clang version 12.0.5 (clang-1205.0.22.9)
Target: arm64-apple-darwin20.4.0
Warning appeared after upgrade to Xcode 12.5 in several files,
example:
In file included from Fl_Scroll.cxx:19:
../FL/Fl_Scroll.H:102:17: warning: anonymous non-C-compatible type given name for linkage purposes by typedef declaration; add a tag name here [-Wnon-c-typedef-for-linkage]
typedef struct {
^
ScrollInfo
../FL/Fl_Scroll.H:104:5: note: type is not C-compatible due to this member declaration
typedef struct { int x,y,w,h; } Fl_Region_XYWH;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../FL/Fl_Scroll.H:128:5: note: type is given name 'ScrollInfo' for linkage purposes by this typedef declaration
} ScrollInfo;
^
|
|
|
|
|
|
- fix issue as proposed
- fix more potential access to uninitialized data issues
- document Fl_Shared_Image::add_handler()
- document typedef Fl_Shared_Image::Fl_Shared_Handler()
|
|
... as requested in this comment:
https://github.com/fltk/fltk/issues/211#issuecomment-814235771
|
|
|
|
Add includes of system headers in the implementation files
where necessary.
|
|
Fl_Scalable_Graphics_Driver
Most coordinate calculations are done with the new inline function
int Fl_Scalable_Graphics_Driver::floor(int coord)
that is used by both the Windows and X11 platforms.
|
|
|
|
|
|
|
|
... as discussed in fltk.coredev.
|
|
|
|
Re: Can custom box type functions handle their own high-DPI screen scaling?
|
